Self Hosted - Self-hosting your services.

11587 readers

29 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

No harassment
crossposts from c/Open Source & c/docker & related may be allowed, depending on context
Video Promoting is allowed if is within the topic.
No spamming.
Stay friendly.
Follow the lemmy.ml instance rules.
Tag your post. (Read under)

Important

Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!

Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.

Cross-posting

[email protected] is allowed!
[email protected] is allowed!
[email protected] is allowed!
[email protected] is allowed if topic has to do with selfhosting.
[email protected] is allowed!

If you see a rule-breaker please DM the mods!

founded 3 years ago

MODERATORS

[email protected]

[Help] My internet disconnected and now Piped doesn't work. (sh.itjust.works)

submitted 3 days ago* (last edited 2 days ago) by [email protected] to c/[email protected]

6 comments fedilink hide all child comments

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 reboot my ISP changed my IPv4 address.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 2 days ago (2 children)

How did you see up the Cloudflare connection? If your ISP rotated your IPv4 address during the reboot, you may need to update the IP in your Cloudflare dashboard. You should be able to use either the IPv4 or the IPv6 address of your server assuming the necessary port has been forwarded/opened in the firewall.

[–] [email protected] 2 points 2 days ago (1 children)

THANK YOU. I didn't realise that my ISP changed my IPv4 address until you commented this. I was about to give up on nginx proxy manager and switch to caddy or something when in reality it was an ip address problem, everything is now working fine.

[–] [email protected] 1 points 2 days ago

Yay!