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

url input not working #14

Open
Timon2023 opened this issue May 22, 2023 · 4 comments
Open

url input not working #14

Timon2023 opened this issue May 22, 2023 · 4 comments

Comments

@Timon2023
Copy link

I installed a voiceping router and changed the ip address. When I drove this address in your application, it says that: Failed to enter, please try again later

@inovramadani
Copy link
Contributor

inovramadani commented May 23, 2023

@Timon2023 can you paste the URL you used? And perhaps also with the screenshots?

"When I drove this address in your application"

Does this mean you test your self-hosted voiceping router with https://voiceping-router-test.netlify.app/ ?

@Timon2023
Copy link
Author

Through this address ws://127.0.0.1:3000 I can go to https://voiceping-router-test.netlify.app/ but I can’t go to this address through your application on android, although they are connected locally. Another question is how to change the server address on the server side? Instead of ws://127.0.0.1:3000 addresses do for example ws://x.x.x.x:3000 ?

@bratello
Copy link

bratello commented Feb 15, 2024

Hi. I also have the issue with url.
I installed the voice router on WSL Ubuntu, propagated the port 3000 to the win host, opened the port 3000 on firewall. The web app https://voiceping-router-test.netlify.app/ works well with ws://localhost:3000, but does not work with the IP ws://192.168.1.xx:3000 - the application is not able to connect to the voice router. Same for VPS SDK Demo app for Android - the smartphone located in the same local network but not able to connect to the voice router. But the smartphone able to connect to the default page page http://192.168.1.xx:3000 - Welcome to VoicePing Router 1.0.0.
I guess the WebSocket should work through the http, so the TCP:3000 forwarding on Firewall should be enough. Can you suggest something?
Also, can you suggest how to enable encryption? Is it possible to enable https on nginx reverse proxy, and forward the decrypted traffic to the nodejs voice router app? Is it enough secure?

A lot of thanks.

@dadangaprasetya
Copy link

Screenshot 2024-03-29 150916

can't you helpme?

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

4 participants