Jump to content

Babble could not connect, try again later.

Closed 2.4.6

replace the file in applications\babble\sources\Settings, with this one. then go to ACP->babble->configuration->general and click save, it should fix the issue. if you don't have ftp access to your server, it will be a few days before i have a new release out.

 

 

Share this comment


Link to comment

okay, run the IPS Support Tool in your acp under support. it will say it has a patch to fix settings not saving. apply the patch. then go to Babble->configuration->general and click save, it should now resolve.

  • Like 1

Share this comment


Link to comment

I think you need to reopen this bug, because we have some major issues concerning the chatservice. 

Really often we are thrown out of the chat room. It is kind of hard to explain, but it seems to happen to all users at the same time. The onlinelist disappear (the icons on the right), and the when we try to write, there is this all so familiar Could not connect to node.js.

When refreshing it is all good. Do you have any errors on your setup on the server you are using that runs node.js?

Share this comment


Link to comment
52 minutes ago, Kjell Iver Johansen said:

I think you need to reopen this bug, because we have some major issues concerning the chatservice. 

Really often we are thrown out of the chat room. It is kind of hard to explain, but it seems to happen to all users at the same time. The onlinelist disappear (the icons on the right), and the when we try to write, there is this all so familiar Could not connect to node.js.

When refreshing it is all good. Do you have any errors on your setup on the server you are using that runs node.js?

this was due to a bug in IPS, a change they made in the settings class on how they saved settings. it would save the URL as url's in the database, but when in the settings store,it would store the object like this:

"babble_settings_node_url":{"data":{"scheme":"https","host":"codingjungle.net","port":null,"user":null,"pass":null,"path":null,"query":"","fragment":null},"queryString":[],"hiddenQueryString":[],"isInternal":false,"isFriendly":false}

they have since patched this, and it saves normally. you seem to be having a different issue, as you can connect but then get "kicked" off. out of curiosity, is it about every 2 hours you'd say?

Share this comment


Link to comment
1 minute ago, Michael said:

y, is it about every 2 hours you'd say?

Sometimes more often - sometimes more seldom... Sometimes it happens to all users in the chatroom, sometimes only one or two.. Sometimes it happens with 5 second between, sometimes it is 2-3 hours... theres no pattern

Share this comment


Link to comment

if you can, try to see what devices it is happening on and/or browsers, it might be something specific to a device/browser that i haven't ran into. i was thinking it was the "refresh"  of the server every 2 hours when it grabs the list of "allowed keys",  as that might be causing it. now i am not sure, i have a new method i've been thinking of doing to get activated keys that would remove the 2 hour wait and make it instant.

give me a few days to test things out, i am still working on the new "commands" structure, to finally get rid of the permissions issues that keeps cropping up, and i need to finish it and test it out before i move onto other things.

Share this comment


Link to comment

It seems like there is a pattern that ALL users are thrown out when I or a Moderator (they are the only one with access) press the Load More button. At least it has happend twice this evening. 

Also - more people with Ipad or Ipad minis are dropping out just only them, not the others.. I'm not sure about these observations at all.

Is there any settings in ACP for babble you would like me to try out?

BTW: a positive aspect abt this is that we always have something to chat abt in babblechat..:) 

 

Share this comment


Link to comment
22 minutes ago, Kjell Iver Johansen said:

It seems like there is a pattern that ALL users are thrown out when I or a Moderator (they are the only one with access) press the Load More button. At least it has happend twice this evening. 

that is weird as that doesn't do anything with sockets at all, that is just an ajax request for more messages, it doesn't send any emits or anything to any other user.

24 minutes ago, Kjell Iver Johansen said:

Also - more people with Ipad or Ipad minis are dropping out just only them, not the others.. I'm not sure about these observations at all.

that is prolly due to more apple dickery with the things they do with JS, i'll look up to see if there are any new "quirks" that iOS 10 and 11 are doing to the JS process that i am not already aware of.

25 minutes ago, Kjell Iver Johansen said:

Is there any settings in ACP for babble you would like me to try out?

none that i can think of, this seems more like an engineering problem than a settings problem.

26 minutes ago, Kjell Iver Johansen said:

BTW: a positive aspect abt this is that we always have something to chat abt in babblechat..:) 

i would prefer the talk be how awesome babble is :)

Share this comment


Link to comment
×
×
  • Create New...