question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

error 'Something went wrong in "await connectionsManager.connect()" in 1.6.1.min.js

See original GitHub issue

here is the client side code, just like the example simple

`

<script src="lib/geckos.io-client.1.5.0.min.js"></script>

<script> ‘use strict’

        var channel = geckos({ port: 2001 })
  
        channel.onConnect(error => {
          if (error) {
            console.error(error.message)
            return
          }
  
          channel.on('chat message', (d) => {
            channel.emit('chat message 2', 'Hello 2')
            console.log('get message', d)
          })
  
          channel.emit('chat message 1', 'Hello 1')
        })
      </script>`

after change to image

it shows

image

the server runs fine with both, no error came out

or did i miss something in version 1.6?

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:10 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
yandeucommented, Aug 2, 2020

Each connection has one channel.

Try connection.channel.userData

0reactions
DolphinIQcommented, Oct 22, 2020

Hey, Im also having the same error when trying to upgrade from 1.3.0 to 1.7.0, running on a local environment image

My code (the relevant parts): client:

this.channel = geckos({
    port: 3000
});

this.channel.onConnect( error => {

if( errorOccured( error ) ) {
    // This console logs the error above
    return;
}

server:

const geckos = require('@geckos.io/server').default;
const { iceServers } = require('@geckos.io/server');

io = geckos({
    iceServers: process.env.NODE_ENV === 'production' ? iceServers : []
});

// express server
const PORT = 3000;
let server = app.listen( process.env.PORT || PORT, () => {
   console.log(`Server started on port ${ PORT }...`);
});
io.addServer( server );

Not sure what Im doing wrong, tried switching ports, and stuff from this thread with no success. Is there a migration guide?

Read more comments on GitHub >

github_iconTop Results From Across the Web

error 'Something went wrong in "await connectionsManager.connect ...
error 'Something went wrong in "await connectionsManager.connect()" in 1.6.1.min.js.
Read more >
[Pool] This socket has been ended by the other party #447
I get this error every once in a while. Not sure why. Can't replicate (yet). I'm using the latest v1.1.1. { Error: This...
Read more >
Bug listing with status RESOLVED with resolution OBSOLETE ...
Bug :1523 - "[IDEA] Offload work by distributing trivial ebuild maintenance to users, ... Bug:107027 - "dev-vcs/cvsd init script for is not working" ......
Read more >
Resolved Problems - Oracle Help Center
The following error messages were thrown: <Warning> <JDBC> <001096> <Refreshing this bad pool connection failed weblogic.common.ResourceException: java.sql.
Read more >
Fix list for IBM WebSphere Application Server V7.0
The following is a complete listing of fixes for V7.0 with the most recent fix ... hung after server recycle due to wait...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found