I am having trouble connecting with my Nextcloud AIO docker setup since a few days and cant seem to put my finger on it. I would be really grateful for some assistance. I seem to be missing something. Here is my issue:
I installed the Nextcloud AIO docker image about 6 weeks ago. Install and setup was pretty smooth sailing and all was working fine up to last week.
Environment:
Nextcloud is running on my Home Server
Host Asustor NAS (default OS wiped and replaced with Debian Bookworm - fully updated OS)
(this server exclusively for Nextcloud: no webservices or containers are running for other purposes.
Networking:
Server is set to a fixed ip and connected over Ethernet to my home router. Portforwarding on the router is set up as usual for ports 80, 443, 8443. That looks to be ok and was working previously.
On install I automatically obtained a Lets Encrypt certificate for my domain name which was also working fine.
So Nextcloud is working fine, but currently my problem is: When I connect from any machine (either inside or outside my home network), I get a long wait and after a minute or so, a time-out with the browser reporting
“The connection was reset”
Only on the server itself, I have no issues loading Nexcloud login page and logging in. When logging in, it shows my server having a valid certificate.
When I ping my external IP from any location, i get a 100% response.
When i ping my domain, I get a 100% response returning the correct ip.
troubleshooting so far:
When I logged into my nextcloud as admin, it showed there was a 400ms throttle on log-in, showing my external IP. I whitelisted that same IP, to see what would happen, but it did not change anything.
No iptable config is running. I installed UFW but disabled it for now
No weird cloudflare or rev.proxy settings
There do not seem to be any relevant error messages in the logs.
I do think this is either an issue with my home routing/port-forwarding, or with my encryption certificate, but I am not sure how to troubleshoot further.
As the Nextcloud AIO is set up as a set of self-initialized Docker containers I find it hard to figure out where to start.
Alright, Sorry for not responding sooner @szaimen . Got swamped by actual work this week
Nevertheless my logs do look weird and possibly bad! Maybe it is a good thing I stopped the apache container. Please advise on the folowing:
2024-11-20T04:00:03.646956316Z Total reclaimed space: 0B
2024-11-21T04:00:08.022898018Z Total reclaimed space: 0B
2024-11-22T04:00:12.391483934Z Total reclaimed space: 0B
2024-11-23T04:00:26.752014770Z Total reclaimed space: 0B
2024-11-23T06:40:53.038510690Z {“level”:“error”,“ts”:1732344053.0382504,“logger”:“tls.cache.maintenance”,“msg”:“stapling OCSP”,“identifiers”:[“www.vriendveen.nl”],“error”:“no OCSP stapling for [www.vriendveen.nl]: parsing OCSP response: asn1: structure error: tags don’t match (16 vs {class:0 tag:28 length:72 isCompound:true}) {optional:false explicit:false application:false private:false defaultValue: tag: stringType:0 timeType:0 set:false omitEmpty:false} responseASN1 @2”}
2024-11-24T04:00:01.126239439Z Total reclaimed space: 0B
2024-11-24T15:15:07.568647951Z Deleting duplicate sessions
I am not really sure what I am reading here, but this seems to be Caddy logs… (I was under the assumption I was running Apache…
But beyond that: It is trying to test a certificate against “app.yinxiang.com”… Why? that has nothing to do with my domain. I do not see an actual data breach but is this a spoofing attempt ??
btw this is only a part of the log. This forum has a limit of 4 url’s per post.
Most of the rest is more attempts to verify that chinese domain. Again I have no idea how/where that came from…
(If you need the entire thing I can post it to some pastebin site. Let me know)
mhm it unfornunately looks like the part of the nc community able to support the AIO is still rather limited
I am wiping this and will do a classic install from source tar.
Hopefully at some point in the future I can come back to this method when it will be an easier experience .
