Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7829179
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 2, 20262026-06-02T10:39:17+00:00 2026-06-02T10:39:17+00:00

In socket.io , when the server is down the client is trying to reconnect

  • 0

In socket.io, when the server is down the client is trying to reconnect to the server and gets the error GET http:/localhost:8181/socket.io/1/?t=1334276656018, that, obviously, because the server is not running and cant serve the connection to the client.

Is there any way to catch this error in the client side?
Something like socket.on("error", function(...){}); can be very handy in this case…

Any suggestions?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-02T10:39:19+00:00Added an answer on June 2, 2026 at 10:39 am

    Sorry about the bother.. i found the solution:

        socket.on('disconnect', function(){
            HANDLE HERE
        });
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm trying to implement a socket server that will run in most shared PHP
I am sending a string down from a websockets server to my client that
I'm trying to determine if a server socket was shut down gracefully or not
So I'm trying to make a client for my server in C#, that accepts
Background I have a simple socket server setup that I am trying to allow
I am trying to write a socket server that forks for every connection. I
I'm trying to get down to the details of what happens once a server
If I kill the Socket Server process, my Socket client process does not receive
I've got a socket server running (it's something that's basically like a chat server).
I am developing a socket server where a client will be bound after being

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.