I am trying to send requests to Zoom API via a HTTP request. When testing on my local machine it works perfectly but when I try it on our production server I get the following error:
msxml6.dll error '80072efe'
The connection with the server was terminated abnormally.
We use Cloudflare for security with our website, does anyone know what the resolution here maybe?
The server is running on Windows Server 2008 R2 using IIS 7.5.
I found the cause of the issue.
It wasn't CloudFlare, it was the server object I was using in my function.
I changed the following line from this:
Set ServerXmlHttp = Server.CreateObject("MSXML2.ServerXMLHTTP.6.0")
to this:
Set ServerXmlHttp = Server.CreateObject("MSXML2.XMLHTTP.6.0")
Problem solved.
Related
I have a nodejs web app with websocket , when i run on localhost it's not problem but when i run on public host (have SSL,domain name...) i get error : WebSocket connection to 'ws://127.0.0.1/ws' failed .
Question here is, where are you trying to connect from
Client OR Server
The error message would indicate you are trying to connect to a localhost, so if you are getting this message back from the client side, then its because your connecting to a non-reachable WS instance. Also, if you WS host is https, you would use WSS protocol vs just WS
As mentioned, without seeing the code its hard to tell
You need to setup your server environment, is your web-server (Apache, nginx) correctly pass requests from world to your node app?..
Is your server firewall pass WS connections?..
IMHO you need a consultation from your provider DevOp's support team.
You are using the following according to your statement:
ws://127.0.0.1/ws
From what I have read in the various ws api's while researching my own websocket issues I believe you would need to make the following change:
wss://127.0.0.1/ws
as wss is used for SSL connections.
This is probably something very simple. I set up a simple ASP-based web server on Server 2012R2 and IIS6. The IP address of the web server is 192.168.18.142. I then opened up a browser (Chrome). Any of these URLs bring up the website on the web server just fine.
http://localhost/
http://127.0.0.1/
http://192.168.18.142/
Then I went to a different machine (behind the same router), opened the browser and tried to bring up:
http://192.168.18.142/
However I received this error in the browser:
500 - Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed.
I even tried turning off the Windows Firewall on the web server to no avail. Any idea what configuration settings to look at?
Why does the URL work when on the web server but not from other machine?
I have a video streaming API developed in Node.js using the Express module.
This API is hosted on my local machine under IIS 8.5 using iisnode module, which makes the IIS as my reverse proxy server and the express (node) as my web server.
When I hit my API URL in the browser, it plays the video for a while and then I get net::ERR_CONNECTION_RESET error.
I get this error after few minutes (approx 7 mins.), but there is no specific time duration observed.
I see below two errors in HTTPERR folder under "C:\WINDOWS\system32\LogFiles\".
2019-05-09 14:55:39 ::1%0 64836 ::1%0 3005 HTTP/1.1 GET /api/videolib/streamvideo?id=f80b4ae0725f11e9b42fcb6803fde91b - 8 Connection_Dropped VideoLibrary.WebAPI.Node
2019-05-10 08:51:02 ::1%0 54848 ::1%0 3005 HTTP/1.1 GET /api/videolib/streamvideo?id=f80b4ae0725f11e9b42fcb6803fde91b - 8 Connection_Abandoned_By_ReqQueue VideoLibrary.WebAPI.Node
I have observed that, I don't get this error at all when I run the API directly under Node.exe thus bypassing the IIS and IISNODE altogether on my local machine.
However, I have no choice but to use IIS and IISNODE in production.
UPDATE:
So, I created an API in .NET equivalent to my node API, and hosted it in the IIS; it works fine without issues of any kind.
Now, I know that there is something weird going on with the iisnode module.
I have tried changing couple of settings in iisnode via web.config, but nothing seems to fix this problem.
Any help on this would be greatly appreciated. Thanks.
What could be the possible cause of the error Error during WebSocket handshake: Unexpected response code: 400?
The app is hosted on ubuntu and deployed using the npm mup package. I included my bundled ssl pem file within mup.json.
Is there anything else that I need to configure on the server?
This can be caused by one of the three reasons:
Some ISPs may use proxies which don't support websockets. This is more apparent over 3G networks
If your app has crashed. Meteor tries to connect to the server and can't since it's not online.
This can also happen if Nginx isn't configured to use WebSockets, and your MUP instance is sitting behind a WebSocket.
So if your app is working as expected (maybe just takes a bit too long to get connected) & has this error in development console it's likely due to a proxy server. To avoid this try getting SSL (https://) installed on your server too. This way the ISP or proxy is not able to alter your app's connection.
I had this error when I was connecting via a hotel WiFi. The problem was that you are always connecting to the internet via their proxy.
My solution to this was to use my mobile phone as a Wifi hotspot. I have Android 6.0.1, and you can access the menu through:
Settings > More > Tethering & portable hotspot > Set up Wi-Fi hotspot (and then enable 'Portable Wi-Fi hotspot')
I hired a VPS (Windows Server 2008) with the aim of hosting a website. So i configured IIS 7.5 to run a html website. The website reads data (HTTP GET requests) from a little node.js application running on the same VPS on port 3000. I am getting the data as follows:
$.get( "http://localhost:3000/myfunction", function( data ) {
});
Inside the VPS if I go to chrome a type localhost it works perfectly. On the other hand if i insert the VPS's IP address the HTTP calls are not working...
Chromes JS Console says:
Failed to load resource: net::ERR_CONNECTION_REFUSED http://localhost:3000/myfunction
I need the node.js app not to be visible from outside the VPS so that sensible data in the code is not reachable...
I finally managed to solve this using a reverse proxy (IIS's ARR and URL Rewrite) as it is explained in the following guide:
http://www.gitshah.com/2013/06/how-to-use-iis7-as-front-end-to-java.html