Messages

I believe this may be an issue with OPNsense version 25.7.x. In the past, I successfully set this up with the documentation & it was working as of OPNsense version 25.1.7, but on a brand new install of 25.7.x on brand new hardware, it will not work. I'm also constantly met with "Saved settings, but remote backup returned no files."

System > Logs > General shows various errors:

`Error while fetching filelist from Nextcloud '/.' path`
`Check Nextcloud configuration parameters`

I'm getting the same error log message as you are, yet I can also manually reach the Nextcloud instance.

I'm still using the same Nextcloud server which my other OPNsense router (now on 25.7.2) still is able to backup to, but the fresh 25.7.2 install is experiencing what the original poster is also experiencing.

Here is the source code for this plugin if anyone has any ideas on how to fix it.
https://github.com/opnsense/plugins/tree/master/sysutils/nextcloud-backup

Thank you very much! What you suggested worked and now everything appears to be functioning again. The help is much appreciated.

Version running: OPNsense 25.1.7_4-amd64

I have searched around the web and around this forum, but I am still unable to find a solution.

I previously had this working with a Nextcloud server that just used http on port 80 and it worked well. Unfortunately, that Nexcloud crashed so I had to setup a new one and used a self-signed SSL cert for more protection on my local network. This Nextcloud server is internal, so it does not have a FQDN and therefore is not able to use Let's Encrypt for SSL certs.

I know "You have to create an app password and use that instead of the password of your username" as this thread also indicates https://forum.opnsense.org/index.php?msg=149140

I came across this old Issue on Github for "nextcloud-backup: option to accept self-signed certificates", but it was closed by the OPNsense-bot many years ago.

What am I missing?

I'm really enjoying the new dashboard in this release. Thank you!

I am having a strange issue regarding a new interface (separate NIC port) on my OPNsense switch. I have two interfaces which have been working fine for the past year, called WAN and LAN (with 192.168.1.0/24 subnet)

I recently created a new interface called LAN2 with a different 192 subnet. The configuration of LAN and LAN2 are identical with the exception of their differing 192 subnets.

It was not passing traffic and the dashboard showed me that it was erroring trying to connect to anything. I thought maybe it was a NAT outbound issue, which was set to autmatic. I tried hybrid and manual while setting rules. Same outcome, LAN and WAN continued to be fine but LAN2 still would not pass traffic.

LAN2 won't ping any systems on LAN or WAN, so I thought maybe it could be a bad NIC port and tried the last NIC port. Same result.

I'm not sure what I'm missing here and hope you all have some ideas I can try. Thank you.