Ticket: Docker Port Change Results in 400 Error on Auth
@Fluff Just created a ticket
Question: Hello, I started my docker instance with docker-compose up - but when auth I have a 400 error. I had to tweak the port 5000 from the docker yaml because I am running on mac and controlce is using this port. However my docker knowledge is limited - I must not have been properly setting it up.
Attempted: try changing the port everywhere from 5000 to 5001
Working On: a moodle plugin to plug to postiz
Using Postiz On: docker-compose
Take it from here @Postiz
Question: Hello, I started my docker instance with docker-compose up - but when auth I have a 400 error. I had to tweak the port 5000 from the docker yaml because I am running on mac and controlce is using this port. However my docker knowledge is limited - I must not have been properly setting it up.
Attempted: try changing the port everywhere from 5000 to 5001
Working On: a moodle plugin to plug to postiz
Using Postiz On: docker-compose
Take it from here @Postiz
7 Replies
I forgot to mentioned, I am trying to make it work in localhost (MacOS).
I found out why the login always come back to login - the app does not work on Safari MacOS (at least in localhost) - somehow it can not connect - however Chrome MacOS can connect. Must be a bug.
Had the same issue
To free the 5000 port you can go to you general settings and switch of airplay
That way you won’t have to update the port in the docker
Thanks. I prefered updating the app port - I was not super comfortable disabling a core Mac feature (the above yaml docker compose works)
I ended up to disable airplay - I had too much trouble when uploading on youtube as it tried to access 127.0.0.1:5001 so I did not use the above yaml in fact. Thanks Beaudelaire. Not that easy 🙂
that would be nice if the project move away from a port that is quite so much used on Apple ecosystem
Hi @Fluff Please select an action
I have the same problem