6
submitted 5 days ago* (last edited 4 days ago) by amogussussywussy@sh.itjust.works to c/selfhosted@lemmy.world

I was turning on IPV6 in my router settings, and in order to do so, my router had to reboot, and without thinking, I went ahead. I then realised, my server is connected to said router, so after the router rebooted, I checked and saw that most of the docker containers were fine, except for the Piped container.

When I go to the Piped instance that's hosted on my domain, it just brings up a Cloudflare Code 522 Error (I use Cloudflare)I tried restarting the containers over and over again but no luck. Any advice? I will provide more information if needed.

EDIT: It's now solved. Apparently during the router reboot my ISP changed my IPv4 address.

you are viewing a single comment's thread
view the rest of the comments
[-] asudox@discuss.tchncs.de 1 points 4 days ago* (last edited 4 days ago)

I haven't really used Nginx, but from a quick look nginx seems to be restarting everytime as it attempts to delete some proxy configuration (?), but fails to do so with code "ENOENT" which just means that such file or directory does not exist.

I also found this issue in the nginx github repo: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3497

According to the discussion in that issue, it seems like nginx is the one causing the problems. Consider downgrading the nginx container image to what it was before if it updated itself.

It also could be something being corrupted, so you might need to dig some more into this matter.

People also recommend switching to other reverse proxies like caddy and traefik. I also recommend it, you might as well take this as a opportunity to use something better. I personally recommend Caddy, as it is very simple to configure and very convenient. It handles HTTPS and all that boring stuff for you. Iirc it also has a cloudflare module, so you can just follow the guide in the documentations to let Caddy automatically renew certs for you via access tokens.

Thanks for the help! I guess I might as well use Caddy since Nginx is screwing me over.

[-] asudox@discuss.tchncs.de 1 points 4 days ago

np, feel free to reach out again if any problems occur.

this post was submitted on 20 Dec 2024
6 points (66.7% liked)

Selfhosted

40717 readers
329 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 2 years ago
MODERATORS