Comment on Help request : Docker service (PeerTube) doesn't have the same way on new server
utopiah@lemmy.world 4 days agoOops 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!
foggy@lemmy.world 4 days ago
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 🤓
utopiah@lemmy.world 4 days ago
Running and healthy
Indeed and they don’t exit.
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.
I checked error logs of all containers and seems fine. The only error I see are client side.
foggy@lemmy.world 4 days ago
Are the two servers on the same LAN? Did you update all configs for the new servers address?
utopiah@lemmy.world 3 days ago
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)