Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I had the exact same issue. My troubleshooting took me to my router. Nat Loopback and hair pinning.
Your router might have some options relating to NAT loopback or hairpinning. Apparently this can happen if your router recently had an update or if it was restarted abruptly and didn’t boot properly.
Try restarting your router. It didn’t work for me and my router is too basic for those options so in the end I took down my Nextcloud and remade another container and started from scratch. I had all sorts of things fucked with my instance so it just made sense to toss it out and fix it again.
Hope it works for you!
Thanks for the response but restarting the modem/router didn't change anything, nor did creating a new container/NGINX config.