What do you mean "doesn't have the same way"?
this post was submitted on 09 Nov 2025
16 points (90.0% liked)
Selfhosted
52916 readers
508 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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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 2 years ago
MODERATORS
Oops sorry, terribly phrased, I meant "doesn't behave the same work" but I simplified, hopefully.
Basically worked on old server, doesn't work on new!
Is the docker container spinning up and running, or failing and exiting?
Run docker ps, it'll tell you how long your containers have been running or if they exited.
If everything is running then it's most likely network, and I'd need to know how it is you used to access it on the old server (web address? Ip?)
If it's not running then you get to dig through error logs to get to the next step 🤓
Is the docker container spinning up and running, or failing and exiting?
Running and healthy
Run docker ps, it’ll tell you how long your containers have been running or if they exited.
Indeed and they don't exit.
If everything is running then it’s most likely network, and I’d need to know how it is you used to access it on the old server (web address? Ip?)
It it accessible via the domain name so networking, as least for UI and API, is working fine. Reverse proxy does let traffic go through.
If it’s not running then you get to dig through error logs to get to the next step 🤓
I checked error logs of all containers and seems fine. The only error I see are client side.
Are the two servers on the same LAN? Did you update all configs for the new servers address?
Different networks entirely. AFAICT no IP is hardcoded, only domain names which are the same.
But... please feel free to check the URL, it seems to work.
My hypothesis is that the player in the browser, maybe due to WebWorks, had cached the IP of the content. So I was getting the UI/API from the new IP but the content itself (namely video files) from the old IP which might have created some CORS/CSP issues and that the player itself blocked it. (updating the post on the forum with that idea in case others get in a similar situation)