Selfhosted

60451 readers

753 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:

Detailed Rules Post

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.

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!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Nginx Proxy Manager - can't login after server restart (lm.ainyataovi.net)

submitted 3 years ago by Shiimiish@lm.ainyataovi.net to c/selfhosted@lemmy.world

2 comments fedilink hide all child comments

So, I think I ironed out a lot of things to get my selfhosted setup running, but it seems that Nginx Proxy Manager is causing me troubles. When I restart my server, the container with NPM restarts as expected but I can't log into the web ui (the website comes up, but when I try to log in nothing happens) and it also doesn't provide the expected proxy functionalities. I'm not sure what happens - any advice would be welcome. right now my only workaround is to delete the container and make it from scratch, but this also means making all proxy hosts + certificates from scratch as well ...

top 2 comments

sorted by: hot top controversial new old

[–] NettoHikari@social.fossware.space 2 points 3 years ago (1 children)

Did you look at the logs? If you're running through docker compose, that'd be docker compose logs --follow container-name.

[–] Derkis@rammy.site 2 points 3 years ago

I'd add that it might be worth checking out the JavaScript console as well (F12 > console in most browsers), in case the problem is with the login page