Closed clemone210 closed 3 years ago
@timohzbs
Accessing the site trough a windows device on the same network.
Neko takes by default your public IP address and that advertises. If you are connecting from the same network / local network, you need to specify n.eko's local IP.
Please refer for more explanation in my fork's README. https://github.com/m1k1o/neko#getting-started--faq
In your case you are missing this environment variable NEKO_NAT1TO1=192.168.1.28
.
@timohzbs
Accessing the site trough a windows device on the same network.
Neko takes by default your public IP address and that advertises. If you are connecting from the same network / local network, you need to specify n.eko's local IP.
Please refer for more explanation in my fork's README. https://github.com/m1k1o/neko#getting-started--faq
In your case you are missing this environment variable
NEKO_NAT1TO1=192.168.1.28
.
ok that worked well. I now want it to be reachable from outside with nginx reverse proxy. I use nginx reverse proxy manager from here
Can you tell me how my config in docker-compose needs to be changed to use it with nginx reverse proxy?
If you're wanting it to be reachable from outside with nginx reverse proxy, You'll want to get rid of the NEKO_NAT1TO1.
Just note that you cannot access it from a local ip, and only from the outside ip in that case.
If you're wanting it to be reachable from outside with nginx reverse proxy, You'll want to get rid of the NEKO_NAT1TO1.
Just note that you cannot access it from a local ip, and only from the outside ip in that case.
So I can only make it either locally, or via the IP address + opening the ports for it to point to this machine?
That would be correct.
But shouldnt it be possible to run behind nginx reverse proxy, so I can access it with a domain? I mean I can open the site with my domain, but cannot login.
That sounds like a port forwarding issue. Since I run my install of neko from nginx reverse proxy as well.
what is your setup and how does your config file looks like?
My config can be found here https://github.com/nurdism/neko/issues/111#issuecomment-742656957 As for my setup, its a default docker-compose setup
So I can only make it either locally, or via the IP address + opening the ports for it to point to this machine?
Theoretically, you should be able to acheive both, since NEKO_NAT1TO1
is an array. But I never tried it that way.
NEKO_NAT1TO1=<remote-ip>,<local-ip>
So I can only make it either locally, or via the IP address + opening the ports for it to point to this machine?
Theoretically, you should be able to acheive both, since
NEKO_NAT1TO1
is an array. But I never tried it that way.
NEKO_NAT1TO1=<remote-ip>,<local-ip>
gets an error: WRN session created with and error error="invalid 1:1 NAT IP mapping" id=xLxQ6C7aQKSkJTZCFPWOYQ9VS6zdWogY module=websocket
Ive only opened TCP 80 & TCP 443 on my router to my nginx proxy manager. On there ive setup my domain to forward the requests to my docker virtual machine. I have about 15 containers wich are accessable from outside using the nginx proxy manager. What can cause that this does not work?
Ive only opened TCP 80 & TCP 443
You seem to be missing all the WebRTC UDP ports then.
NEKO_NAT1TO1=<remote-ip>,<local-ip>
gets an error
I loked it up, it should be white-space separated, sorry for confusion.
NEKO_NAT1TO1=<remote-ip> <local-ip>
Ive only opened TCP 80 & TCP 443
You seems to be missing all the WebRTC UDP portrs then.
yes it seems to be the upd ports. But I do not know how to fix it unfortunately.
I shows me always a weired IP Address: neko_1 | 11:55AM DBG session ended address=172.30.0.1:40206 module=websocket session=lCE7kGWLzCFNo2ab2cHWa1xOJdxNz70m
yes it seems to be the upd ports. But I do not know how to fix it unfortunately.
You need to open them to the outside as well. Those UDP ports cannot be proxied, because they are not using HTTP protocol, but RTP etc.
UDP proxying is not exactly easy yea, and like @m1k1o said, unlike the http traffic, the udp ports aren't domain bound
Cant get it working with my reverse proxy setup. But project seems to be really great!
Did you never port forward those udp ports or?
Did you never port forward those udp ports or?
I now commented out the network mode as well as the IP changed my nginx configuration and it now works. I as well noticed that I am doing everything from my work and my company restricts all udp traffic. So I tested it from a different machine which was located not at work and it then worked as well.
Glad to hear you got it working
Describe the bug I deployed the docker-compose container as described. After login It gets me this log:
Desktop (please complete the following information): Container is running on a ubuntu server vm. Docker is installed via snap. Accessing the site trough a windows device on the same network.
Server Log:
Client-Log: