Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port 6000 shouldn't be the default port for the settings, as it may lead to errors #727

Closed
vmesel opened this issue Oct 28, 2022 · 3 comments · Fixed by #728
Closed

Port 6000 shouldn't be the default port for the settings, as it may lead to errors #727

vmesel opened this issue Oct 28, 2022 · 3 comments · Fixed by #728

Comments

@vmesel
Copy link
Member

vmesel commented Oct 28, 2022

Port 6000 is restricted by both Chrome and Firefox as a non-web port, making users prone to thinking that the application doesn't work on their device or settings. Maybe we could change the default port to 8080 or something like that.

image

image

image

How to reproduce the error:

Setup your prest.toml or environment variable PREST_HTTP_PORT to 6000. That's all

@arxdsilva
Copy link
Member

Hi @vmesel , this happens because the docker-compose is exporting port 3000 and you're requesting prest to change it to 6000, so internally docker will have the port open but not exposed by the container

@vmesel
Copy link
Member Author

vmesel commented Oct 28, 2022

I've changed the port and it worked, @arxdsilva. These are my files with the port configured.

image

All of those, I've changed to 8080 and worked on browsers.

While using port 6000, I could only use it through cURL.

image

@vmesel
Copy link
Member Author

vmesel commented Oct 28, 2022

In our docs, we have some references to port 6000, as shown below:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants