I am trying the example from http://doc.qt.io/qt-5/qtwebsockets-echoserver-example.html to create a simple websocket server and connect to it via google chrome browser.
I just used the example files, the default port (1234), I built it and the application is running fine "WebSocketServer listening on port 1234". But when I try to connect with the sample html there is no connection. I tried other ports as well.
My problem is I don't know how I can start to debug where the problem is? I don't get any errors or anything. Any ideas what the problem could be? Thanks!
You can use developer-tool of chrome, the "Console" tab will display some error message after websocket connect timeout.
Related
Check https://www.winsteadworks.com console for the error.
My website is on my raspberry pi 3 using nginx webserver to host my website. I am having trouble getting NAF (Networked AFrame) to work correctly. What I am trying to do is get Easyrtc to work correctly so I can interact/communicated with other players on my website. I got this to work correctly while it was hosted locally on my other computer, but when I moved it to the raspberry pi and tried to put it online was when I started to have issues.
I am getting a 403 error for my socket.io for easyrtc. On my website if you look in the console you will see the errors start to stack for socket.io.
What I have tried:
Check port forwarded ports
tried to add port 8080 to my config in /var/www/html/winsteadworks.com but kept getting errors
Checked my firewall settings for both my router and my raspberry pi
I also tried reconfiguring different files but still have had no luck.
The error:
socket.io.min.js:1 GET https://winsteadworks.com/socket.io/?EIO=3&transport=polling&t=MJ1pNxu 403 (Forbidden)
This error continues over and over every second and won't stop until you close the page.
I am at a loss here until I know a few things:
Why am I getting this error? Is this a nginx issue, is this an easyrtc issue, is this a raspberry pi issue, or is it a port forwarding problem (yes port 8080 is forwarded)?
What direction do I need to go in order to problem solve this?
Or I will just take the short, sweet and simple answer! Thanks in advance for you time.
I need to connect to a third party webservice. When I hit the link directly in the chrome browser, I am able to connect to it and I get a response. But when I tried the same using Advanced REST Client app of chrome, I get a message as 'The service's server DNS address could not be found.'
Also, when I tried to connect it via my JAVA code, using spring's rest template, am getting an Unknown host exception. What could be the reason that am able to connect via browser but not otherwise?
Thanks in advance.
Maybe it's a problem with your system's DNS settings? I'm not sure how Chrome handles queries to DNS when primary DNS did not found the record. If it uses Google DNS' then Chrome may connect to the service but other applications can't.
To test it set your DNS to 8.8.8.8 and check if apps start working.
From browser it's working properly but not from rest client or application, then i guess the problem with the proxy.
if you are using your office network, then this issue will come.
Try hitting the webservice by connecting to personal network.
i have faced similar issue last week, from browser and postman i'm able to hit the web service but not from the application.
Ones i connected with my personal then it started working.
Hope it helps.
The problem
I'm having an issue where when I start my local dev server with meteor, about 3/5 times the client's socksjs connection via ddp-client.js isn't able to connect and gets an ERR_CONNECTION_REFUSED error. All other connections work fine (websocket, JS, css, etc).
I'm seeing this in the console
The socks is attempting to connect to 192.168.1.14, which is my correct internal ip.
What I've tried
setting the port manually with meteor --port 3000
waiting for Meteor.status().status === 'connected' on the client before making any calls
If you'd like to recreate the problem yourself you can pull down the package I'm working on, ProseMeteor at commit 51c0a304338228102edc75427f72e689a7aafb8a and try running the app yourself by running the bash run_demo script, you should see the problem when you visit http://localhost:3000.
I appreciate any help!
i created a Myservice.asmx and it's working fine all the methods i am ble to invoke,giving me the correct but when i adding my MyService.asmx to my wwebsite as areferences giving me the following error.
There was an erroe in downloading 'http://localhost:49211/Myservice.asmx'
unable to connect to the remote server No connection could be made because the targer machine actively refused '127.0.0.1.49211'
There was an erroe in downloading 'http://localhost:49211/Myservice.asmx/$metadata/'
aAny Suggestions to solve this....Error..
"actively refused" often means that the connection simply couldn't get through and is usually a firewall / router issue to forward and allow the necessary ports through.
I'm experiencing some really odd timeout issues when running a ASP.NET 2.0 project on Cassini on localhost, and I don't have enough data to get a clue of what's going on.
Is there a way to monitor localhost traffic to Cassini, either using some specific development tool or a general-purpose monitoring app such as fiddler?
Just to pre-empt some answers I'm already aware of:
Normally I can use the well-known dot-hack for using fiddler to monitor localhost traffic, but with Cassini I get the following error message in the browser:
[Fiddler] Connection to localhost. failed. Exception Text: No connection could be made because the target machine actively refused it ::1:3213
Fiddler also listens to localhost on http://ipv4.fiddler:port, and I can intercept the traffic. But when I do this the timeout issues don't occur!
Any other tools or fiddler workarounds welcome! Thanks!
Edit: Oops. This question had already been asked... Twice.. Didn't come up on search or suggestions. The solution found in the second thread is to use the dot-hack with ip-address (http://127.0.0.1.:port/ instead of "localhost". This question may be closed.
While fiddler ignores requests to localhost, it listens to 127.0.0.1. (note the trailing dot):
So this won't work:
http://localhost:1234/
But this will:
http://127.0.0.1.:1234/
You're generally better off using http://ipv4.fiddler as it makes it more explicit what you're trying to do.
CassiniDev is an open source project that was developed to fill in all the blanks left by WebDev.WebServer/Cassini.
You will find this issue handled as well as many others.
It works well as a stand-alone server, as an in-process server suitable for testing and embedding and, most notably, as a direct replacement for the Visual Studio 2008/2010 dev servers.
alt text http://i3.codeplex.com/Project/Download/FileDownload.aspx?ProjectName=cassinidev&DownloadId=123367
alt text http://i3.codeplex.com/Project/Download/FileDownload.aspx?ProjectName=cassinidev&DownloadId=123366