-
Notifications
You must be signed in to change notification settings - Fork 59
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
does not proxy port on linux #87
Comments
May be for some reason |
Thanks for the response. I verified I don't have anything running on port 80. I also verified that rinetd (version 0.62-5.1) is running. However, the /var/log/rinetd.log file is empty. Even after stopping and restarting the rinetd service. Is there another way to verify that it is working? |
I am not sure, what is happening in your setup. Can you paste your
Once Invoker is running. Can you telnet to port |
Contents of
I am able to telnet to port 23401:
Not sure if I should be able to telnet to port 80, but I cannot:
On Ubuntu, I have ufw installed (Uncomplicated Firewall). I don't have it running and have even reset and disabled it through the GUI. No change in behavior. Invoker does run and start the process, it just isn't getting the port proxied. Thanks for all the help so far. PS> Didn't mean to close it. :P Habit I guess. |
thank you. can you also post |
Sure... I didn't customize anything here:
|
I'm seeing the same issue on OS X 10.10 (Yosemite) when installing from master. Not sure where I'd find |
The OSX issue may be separate one and I am currently using invoker master on mavericks and it is working just fine. May be a 10.10 problem, which we will look more closely if one of us gets hold of a @brainlid it appears to be |
I have a similar problem on 14.04. I think it might be an RVM issue or maybe zsh? those are really the only variables on my machine that are different. note I can't even get to site:port... although it works if I use localhost:port Update: Scratch the almost the same problem, I am having the exact save problem as this issue. On Ubuntu 14.04 with rvm and zsh. The almost the same problem I was seeing was because I was connected to my work Cisco VPN. When I shut down the VPN I have the same issue as above, although I need the VPN up to work, so this may be a deal breaker. |
+1 to described problem. I can access site from http://site.dev:9001, but can't from http://site.dev. However on the other machine with the same configuration everything works just fine (Ubuntu 14.04). |
I am also using RVM, if that is a factor in the problem. |
@brainlid I guess last resort is, giving one of us access to the boxes where this is problematic. cc @szyablitsky |
@gnufied It is my development laptop, so that isn't an option. |
Same problem here unfortunately :( |
i will re-check this issue on ubuntu, and update this thread, thanks. |
@iffyuva sorry scratch me from that list, I thought I was affected, turns out I had a subtle typo in the .dev URL. Error reporting may be improved tehre but definitely my fault. |
Is there any update on this? I'm having the same issue on Ubuntu 14.04.3 with RVM and zsh. |
Can anyone try this with latest master and let me know? However, latest master will not work on Ubuntu 14.04 because now Invoker only supports Linux distributions that use systemd. |
I've found what caused my issue. It was related to prax and his firewall iptables nat rules. If someone has the same issue just do iptables -t nat -L -n -v to preview the rules. If there are any redirections on ports 80(http) and 443(https) then do this command to clean your rules iptables -t nat -F After this you could use invoker http .dev domains. Anyway @gnufied I'm using 1.4.1 version of invoker on Ubuntu 14.04.3 and it works fine. Can you guys at least make a special branch for Ubuntu 14.04 users when you update the gem to a version that uses systemd? |
Just wanted to add here that I'm experiencing similar issues on Sierra 10.12.5 . I understand this might be different because it's not Unix specific. Can not access via
I'm curious if anyone knew any other things I could check out. I'd love to contribute to this repo. |
I still have this issue as well on Ubuntu 16.x I would love to help contribute to this fix. |
I'm using Ubuntu 13.10 as a development machine with Ruby on Rails. I ran the invoker setup and appear to have everything setup correctly.
Example config file:
[qlp]
directory = /home/mark/dev/qlp
command = bundle exec rails s -p $PORT
I can start the process and verify it works. However, it will ONLY respond if I explicitly add the port to the url. (must do http://qlp.dev:9001). It does not respond without the port being added.
I checked the /etc/rinetd.conf file and it looks like it should be proxying the port.
The text was updated successfully, but these errors were encountered: