Can't access Nextcloud locally but I didn't change anything - help!

I have encountered a strange problem with my setup.

My nextcloud is in Docker, and is hosted on a local machine. I have a domain name set up through cloudflare and nginx proxy manager within docker to access nextcloud. It has been working fine for months.

Additionally, I’ve been able to access nextcloud locally through local IP.

What’s strange is that nothing about my setup has changed, but I seem to have lost the ability to connect to nextcloud.

If I try to access via the domain name, cloudflare tells me my host is not working.
I know my server is online, I can ping from it.
I know my server is online, I can ping from it on the command line, and
I can access portainer, which I use to manage docker, locally via the IP address.
Portainer tells me the nextcloud container is up and running fine.

My hope is that I can still reach the nextcloud login page if I use my ip:8888 and specifically use http:// and not https://.

However, once I enter a username and password, I am redirected to https://address

And get SSL errors:

Secure Connection Failed

An error occurred during a connection to 192.168.1.XXXX:8888. SSL received a record that exceeded the maximum permissible length.


The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.

I get SSL errors no matter what browser I use. I assume I have a force https:// set within nextcloud because I can’t seem to navigate around it via browser settings. And I can’t login to change that.

Any ideas what I can do? I’m not even sure the best logs I can provide. And again, I didn’t change any settings from when it had been working regularly :frowning:

Hope you can help - I’ve loved being in control of my data.

The SSL errors on different URLs are probably due to HTTPS redirects and not related. Just for reference, this is from the overwriteprotocol setting which can be changed via occ.

Have you looked at the docker container log?