websocket connection closed before established laravel on ubuntu server? - laravel

I have implemented websocket in laravel framework. It is working fine on localhost windows OS but giving error on live ubuntu server
["Connecting",{"transport":"ws","url":"ws://IP-Address:6001/app/qwerty?protocol=7&client=js&version=7.0.0&flash=false"}]
I think this is error because port is not allowing to connect. but i am not sure about it. What should i do? I am using aws webservices
Added rule

Related

unable to access spring boot application deployed in centos 9 server : request time out

My application was developed in Spring Boot, MySql. My server is running on CentOS 9 Stream. port 8080 is ocupied by Jenkins. So I have deployed it in a different port 8081. But my problem is when I am trying to access the API from the postman, it is taking a long time and at last showing message request time out.
How I can resolve it?
I am also facing the same issue in the time when trying to access the MySQL from DBear, it is taking a long time to connect and after that telling that request time out.
After searching in the i think the issue is with the port availability from the server. Guide me so that when I will deploy an application it will be available. I am also Apache web server.
maybe you have some rules on 8181 port, to check all the policy on Linux firewall get all the rules of iptables in cent-OS by this command.
sudo iptables -S

POSTMAN Error - Could not get any response

I have a VPS Server where I installed Laravel-5.8 for the backend. Also, I installed XAMPP and made the Laravel Application to be on Port 8888. The VPS server is 10.10.10.7(not the real IP). On the VPS server, I tried to test using POSTMAN:
http://10.10.10.7:8888/backend/api/login
http://localhost:8888/backend/api/login
Both work perfectly on the server. However, when I tried to test using POSTMAN from an external system with:
http://10.10.10.7:8888/backend/api/login
I got this error:
How do I resolve it?

Socket.io not accessible via domain name

I have a socket.io node js application running on server on port 3001. When I access that socket connection via browser http://ip-adress:3000/socket.io/?EIO=3&transport=polling&t=1502735738006-0 It works perfectly fine.
I have a VPS on vultr with Ubuntu 14.04 x64
And I have a domain jackpotrolldice.com pointing to that server.
When I try to access via browser like http://jackpotrolldice.com:3000/socket.io/?EIO=3&transport=polling&t=1502735738006-0 then it doesn't work and connection timed out error comes.
As I am new to nodeJS and socket.io. So please guide & help me!Thank you in advance!

i'm trying to share localhost with ngrok

i'm trying to access my localhost via ngrok, and my project is Laravel 5.3
The connection to http://****.ngrok.io was successfully tunneled to your ngrok client, but the client failed to establish a connection to the local address localhost:8000.
how can i solve this issue ?
Kindly check if you tunnel same port which is used by your application like 8000.

Deploying Socket.io on a windows server

I have a basic chat socket.io node.js application working on the localhost of a Windows server running Windows 7.
Node and Socket.io installed without any issue and when I run my application through RDC to the windows server, the socket works perfectly.
What I'm struggling with is how i access the socket e.g. "socket.io/socket.io.js" externally.
I would have assumed it would be rather than "localhost:8000/socket.io/socket.io.js" it owuld be "{server_ip}:8000/socket.io/socket.io.js" however this does work.
I saw some discussion about iisnode, but it seems that sockets arent supported yet with that implementation.
Any suggestions?
You can use socket.io with iisnode, however you will not be able to use the websockets transport since IIS 7 does not support websockets. You must explicitly configure your iisnode-hosted socket.io server to use the xhr-polling transport instead.
It turned out to be a firewall issue that was blocking access to that port which my hosting company managed to resolve for me so I'm using socket.io in the normal manner through a node command prompt.
Thanks for the advice, I did try Iisnode and like you said found that sockets weren't supported.

Resources