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

Caddy cannot open ports 80 and 443 #91

Closed
jhit opened this issue Feb 6, 2024 · 4 comments
Closed

Caddy cannot open ports 80 and 443 #91

jhit opened this issue Feb 6, 2024 · 4 comments
Assignees
Labels
wontfix This will not be worked on

Comments

@jhit
Copy link

jhit commented Feb 6, 2024

Hello.

I'm new to devenv and I had quite some issues with the fact that processes running under non-privileged user account cannot access ports below 1024.
At least that was my experience on Ubuntu 22.10.

11:31:32 caddy.1           | Error: loading initial config: loading new config: http app module: start: listening on :443: listen tcp :443: bind: permission denied

For me this was a huge bummer because it took me a lot of time to find the reason why my devenv would not start.
Maybe you could consider to use ports above 1024 like the default setup used in the Shopware documentation. They use port 8000.

@lx-wnk
Copy link
Contributor

lx-wnk commented Feb 6, 2024

Hey @jhit thanks for the feedback. Currently, we don't plan to reverse the change regarding the ports.
But we made an attempt to ensure that you're able to use our setup in the future. To achieve this, you can change your http and https port to your liking.

You can also change most of the other available ports.

Hope that helps

@lx-wnk lx-wnk self-assigned this Feb 6, 2024
@lx-wnk lx-wnk added the wontfix This will not be worked on label Feb 6, 2024
@jhit
Copy link
Author

jhit commented Feb 6, 2024

Fair enough. But mybe you could at least add a hint in the documentation to help other newcomers.

May I ask why you do not seem to have this issue? Are you using this setup on OSX or in Docker Containers? I have no idea why s.o. else could run this on Linux without having issues.

lx-wnk added a commit that referenced this issue Feb 6, 2024
lx-wnk added a commit that referenced this issue Feb 6, 2024
@lx-wnk
Copy link
Contributor

lx-wnk commented Feb 6, 2024

But mybe you could at least add a hint in the documentation to help other newcomers.

Thats a good point, I added a hint to the docs via #92

May I ask why you do not seem to have this issue? Are you using this setup on OSX or in Docker Containers? I have no idea why s.o. else could run this on Linux without having issues.

Seems like that. We are working on MacOS and there hasn't been an error like that.

@lx-wnk lx-wnk mentioned this issue Feb 6, 2024
2 tasks
@jhit
Copy link
Author

jhit commented Feb 6, 2024

Thank you very much.

@jhit jhit closed this as completed Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants