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

Black Screen Issues while using private docker container behind a nodejs proxy server #401

Open
atomiccoder45 opened this issue Jun 21, 2024 · 17 comments

Comments

@atomiccoder45
Copy link

Black Screen Issues while using private docker container behind a nodejs proxy server

@m1k1o
Copy link
Owner

m1k1o commented Jun 21, 2024

Check out troubleshooting guide: https://neko.m1k1o.net/#/getting-started/troubleshooting

@atomiccoder45
Copy link
Author

Hi @m1k1o tried this solutions but it is not working,

I am following below way for my approach

Creating Docker containers without exposing them.
Proxying with a Docker container hosting a Node.js proxy server. Both are in the same network, and proxying is done via TCP port.
It often shows a black screen but sometimes works.

@m1k1o
Copy link
Owner

m1k1o commented Jun 21, 2024

You must have your ports (UDP and/or TCP) available from outside. If you want "proxy for webrtc" then you need Turn servers. https://neko.m1k1o.net/#/getting-started/?id=using-turn-servers-instead-of-port-forwarding

@atomiccoder45
Copy link
Author

Hi,

I have used google stun server like below:

NEKO_ICE_SERVERS='[{"urls": ["stun:stun4.l.google.com:19302"]}]'

still it says peer connection state failed in logs and show it as a black screen

@m1k1o
Copy link
Owner

m1k1o commented Jun 21, 2024

Stun server is only to discover your peer's IP. There is no data flow, ports still needs to be accessible. You need Turn servers. Either own or paid service.

@atomiccoder45
Copy link
Author

Hi,

I have tried couple of turn servers, but it sometimes suddenly peer gets disconnected and screen turns black

@atomiccoder45
Copy link
Author

When url reloads websocket connection of neko chrome gets disconnected

@m1k1o
Copy link
Owner

m1k1o commented Jun 23, 2024

It should be reconnected. Try setting higher read and write timeout on your proxy. To at least 60sec.

@atomiccoder45
Copy link
Author

tried it still whenever it has a reload it appears to be a black screen

@atomiccoder45
Copy link
Author

@m1k1o Hi, we are having a big release, appreciate a quick support from you to solve this issue

@m1k1o
Copy link
Owner

m1k1o commented Jun 24, 2024

If you would like to have priority support with immediate help tailored to your needs, please take a look at the sponsors dashboard:

https://github.com/sponsors/m1k1o?frequency=one-time

@atomiccoder45
Copy link
Author

Hi,

I have sponsored you, please check the dashboard, and please support us with immediate basis

@m1k1o
Copy link
Owner

m1k1o commented Jun 24, 2024

Hi. Still didn't receive anything. Could you join the discord and write me DM or write me on the contact address that you received after you sponsored me. So that i can get directly in touch with you and resolve your issue immediately.

@atomiccoder45
Copy link
Author

Hi yes how can i join you on discord

@m1k1o
Copy link
Owner

m1k1o commented Jun 24, 2024

There is join link in readme, you can find me in the room:

Chat on discord

@atomiccoder45
Copy link
Author

I have messaged you in the chat

@atomiccoder45
Copy link
Author

Hi @m1k1o, please dedicate some time of your time for a call, we can connect and you can help me to close this issue

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

No branches or pull requests

2 participants