Debugging Issues with Websockets

[patrick]

@Alexander_Paladines

Hi @patrick, the update works, but at half, now it get load at first without problem, before, the API get hang up. Now, when the “Refresh Server Action” it’s called in the API it doesn’t work.

In an API in the Server Action when reach the step of “Refresh Server Action” in browser XHR tab the API show up in Status (pending), like if the API doesn’t complete the proccess and never change the Status.

It seems that the refresh action also needed to be updated, it invalidates the Redis cache for the specific server action but was still using the old Redis api.

sockets.zip (1.1 KB) unzip to lib/modules.

[Alexander_Paladines]

Cool, it works now. Thanks

[tbvgl]

Downloading and applying all three zips from Patrick fixed all my issues with emits and crashing sockets as well.

[AdrianoLuiz]

Cool it worked here too.

[Alexander_Paladines]

Hi,

@Alexander_Paladines

Cool, it works now. Thanks

I know that I already said that it’s working perfectly, and it’s true, but, now testing in remote server I realize this:
My remote server has redis installed but is configured with a password to access to redis:
My redis installation is based on this steps:

Cómo instalar y proteger Redis en Ubuntu 20.04 | DigitalOcean

Specifically step 4 where I uncomment #requierepass

In pm2 logs I obtain this:

server-connect:setup:config redis connection failed, [ErrorReply: WRONGPASS invalid username-password pair]
You have triggered an unhandledRejection, you may have forgotten to catch a Promise rejection:
Error: WRONGPASS invalid username-password pair
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
[ErrorReply: WRONGPASS invalid username-password pair]

I already tested the password using redis-cli in terminal and it works normally, with Wappler v5.6.2 this was working without problem. And of course if I deactivated Redis from Server Connect Settings the message dissapear.

Too I have comment the #requierepass to remove auth from redis and in Server Connect Settings in Wappler I had to change to redis://localhost:6379, doing this I get correctly in logs:
server-connect:setup:config redis connected

My .ENV for redis is:
"REDIS_URL": "redis://myPassRandomRedis@localhost:6379",

So, I think that redis auth is not working properly with this version.

[tbvgl]

Looks like you did not specify a user in your connection string. @Alexander_Paladines

[Alexander_Paladines]

Thank @tbvgl you are right. User was not defined.

"REDIS_URL": "redis://:myPassRandomRedis@localhost:6379",

Strange is how this was working before in v5.6.2 without issues.

Even in production server I have this format, because I don’t update the project since v5.6.2.
"REDIS_URL": "redis://myPassRandomRedis@localhost:6379",

Now in Staging v5.8.1 I have to add : for the missing user.

[tbvgl]

I guess there was a default user defined before the update. Glad it works for you now.

[Teodor]

Fixed in Wappler 5.8.2

[sylvainbaron]

Hi,
Just updated wappler to 5.8.2 and all my sockets="true" serverconnect does not work anymore…
I tried updating the 3 files from this topic with the same NOK result.
Thanks for your feedback

[daves88]

I just updated to 5.8.2 and I am having this problem. I was not having this problem on 5.8.0 and everything was working great! I should never have updated. I don’t use Redis.

Does anyone know wtf is going on with this update? My whole site is broken as I am not getting in results from my database!!

[umadmin]

+1 to the other comments. 5.8.2 did not fix the websocket issues. I’m using the standard wappler redis db.

[daves88]

I am not using Redis and have the same issue… seriously guys this is paralysing my app!

[daves88]

Not fixed - I am not using Redis and getting an error. Do you have a copy of v5.8.0 for OSX? Urgently needed until this is fixed please