7
submitted 2 days ago* (last edited 1 day 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
[-] scott@lem.free.as 4 points 2 days ago

It sounds like your port forwarding settings weren't saved and the reboot has gone back to a previous configuration.

this post was submitted on 20 Dec 2024
7 points (70.6% liked)

Selfhosted

40678 readers
314 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