this post was submitted on 29 Oct 2023
-1 points (0.0% liked)

Selfhosted

39824 readers
643 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Hi all!

I’ve had Nextcloud installed on Docker and it has been working for a while until now.

I had to change my server from wifi to Ethernet and gave it a new static IP. I also uninstalled docker and reinstalled it so I’d be starting fresh.

I have Nextcloud working and when I go to localhost:8070, Nextcloud works properly. When I use another device connected to the same network by wifi, it doesn’t work.

I made sure the config.php file has the server’s static IP address listed in the trusted domains category.

This used to work before but now after hours of troubleshooting, I’m all out of ideas and frustrated 😩 Any help is appreciated.

EDIT: My wife to stroll by and casually was all “did you check Windows Firewall?” and lo and behold, Windows Firewall chose today to block private connections on Docker Desktop backend -_-

Once I enabled it everything worked perfectly. Leaving this up here in case someone else stumbles upon this exact issue.

top 2 comments
sorted by: hot top controversial new old
[–] maiskanzler@feddit.de 0 points 1 year ago

Have a look into the logs of nc and see if it complains about a trusted proxy or similar. The ip range within a container network often changes between resstarts and that was a problem for me with my reverse proxy setup.

[–] 9488fcea02a9@sh.itjust.works 0 points 1 year ago

What is the error you get when you try to connect from another device? If not a webserver error, then maybe a firewall issue. Docker might do weird things to your firewall rules when you first install