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
Permission denied on port 80 & 443 #17
Comments
|
Hi @mekanics ... what a strange.... setcap is applied successfully as you could see at Dockerfile.... I've started the package right now with the parameters you tell me and it's working well.... May be you have another service exposing the port 80?? Could you try for example 81?? Port 443 fails too?? As you can see, trying to reproduce your issue...It seems to work well... Best regards.... |
|
hi @rawmind0 thx for your help. hmmm... and no, port 80 is not used by an other service this is getting really weird |
|
Hi @mekanics... It's so strange the issue that you have... I run it from the catalog and it works ok... It's annoying.. How are you launching that?? What kind of hosts are you using?? Are you using AUFS, apparmor seccomp...?? I think AUFS doesn't support xattr (setcap) in all versions... This is my log, launched from catalog, listening at port 80, in my rancher system....As you can see, it starts without any problem..... In order to help you a little, i need to be able to reproduce the issue.... Best regards.... |
|
i have the same issue: debian 8 Running traeffik with 8080 and 8443 works as expected. EDIT: tried running Do you mean with AUFS the file mounts docker create? |
|
Hi @Munsio... this issue is so strange. i've tried to reproduce it but i didn't get it. I'll try different things in order to know why it's happening. Most of the people doesn't suffer it, then i guess that it would be an issue with one piece or a specific version or parameter of it, docker, aufs, kernel,....I'd like to but i don't know by the moment, just speculation. As you can see at Dockefile, I'll continue looking for the root cause of this issue. Best regards,... |
|
Have you made any progress on this one? I have the same issue as already covered in this issue. |
|
Not sure if this is a solution for traefik, but Instance settings, where port 80 is the only inbound port exposed in the security group: I ran the following command from ssh, but the server exited with an error: I found that I needed to run the program's The result that worked for me (no error): |
|
Happened to me also. Traefik ran correctly for many months until on one of the hosts it happened: |
|
Hi guys, @mtso , you don't need to run traefik command with sudo. Traefik binary has @mariusstaicu , what has changed in one of your hosts?? Update/Upgrade?? Config change?? The problem could be related to selinux or with another host configuration. In coreos is solved disabling selinux in docker execution, #18 Best regards.... |
|
Please, reopen if it's needed. |
|
My Connection blocks most ports on the network. I have 80 and 443 as open ports. I want to access my EC2 application on the port 80 and 443 not on 8888. Please help. I get this Error when I set port to 443. |
|
@TheBali - Have you got the solution? I'm facing same problem too |
|
@TheBali - I'm also having the same problem. Did you find a solution? |
|
Hey guys, Traefik is able to run on priviledge ports, under 1024, due to traefik binary has setcap 'cap_net_bind_service=+ep' ${SERVICE_HOME}/bin/traefik Which os are you running?? Do you have enabled selinux or similar?? The problem could be related to selinux or with another host configuration. In coreos is solved disabling selinux in docker execution, #18 @TheBali, what are the logs you attached?? Don't seem logs from traefik... |
|
Hi @rawmind0 , thanks for getting in touch. I'm running Windows 10. I get the problem whenever I run traefik.exe (any version) The full error is: |
|
Hi @cpatte7372 , sorry, but i don't know how traefik is working on windows. This repo is a docker for running it at linux. I think you should check Traefik docs and if it's not working properly, open an issue on traefik repo |
|
@rawmind0 thanks anyway. Maybe someone who looks at this thread might be able to help |
|
I don't know if anyone ever posted this, possible answer, but I have been using traefik successfully ubuntu 16 but tried it today on an Ubuntu 14 instance and got this error. |
|
I'm also having the same problem. |
|
Don't reopen this (this necro only for necroposters), these are privileged ports (0-1023 precisely) which require the process to run as superuser. Anything above (1024+) your OS will allow to be bound by users too. |


I'm trying to start traefik on rancher with the latest template (v1.0.3-rancher1) and the following setting:
With this config the server is not able to start and I'm getting the following error:
I was able to start traefik with http only on port 8080.
I believe it has something to do with
setcap 'cap_net_bind_service=+ep' ${SERVICE_HOME}/bin/traefik, which should work in my opinion...any ideas?🍺
The text was updated successfully, but these errors were encountered: