Hi folks, today I messed up something on my system, I don’t know what exactly but now my slack and discord (desktop apps) are not working.
I think it’s something that has to do with sockets, discord cannot open at all while slack works but with no live updates.
Here are some logs form slack
warn: SOCKET-MANAGER (E01HSMSV622) Socket was closed because #1006: generic error
info: [SOCKET-MANAGER] (E01HSMSV622) Changing from prov_connecting to error
info: [SOCKET-MANAGER] (E01HSMSV622) will stay in error state for up to 10000 ms
info: [SOCKET-MANAGER] (E01HSMSV622) Changing from error to wait_for_rate_limit
info: [SOCKET-MANAGER] (E01HSMSV622) will stay in wait_for_rate_limit state for up to 120000 ms
info: [SOCKET-MANAGER] (E01HSMSV622) backing off: will wait for 13567 ms
info: [SOCKET-MANAGER] (E02TKJ81FMW) Changing from wait_for_rate_limit to connect
info: [SOCKET-MANAGER] (E02TKJ81FMW) will stay in connect state for up to 10000 ms
info: [SOCKET-MANAGER] (E02TKJ81FMW) Changing from connect to checking_fast_reconnect
info: [SOCKET-MANAGER] (E02TKJ81FMW) will stay in checking_fast_reconnect state for up to 60000 ms
info: [SOCKET-MANAGER] (E02TKJ81FMW) Attempting to connect to primary region
info: [SOCKET-MANAGER] (E02TKJ81FMW) Changing from checking_fast_reconnect to prov_connect
info: [SOCKET-MANAGER] (E02TKJ81FMW) will stay in prov_connect state for up to 10000 ms
info: [SOCKET-MANAGER] (E02TKJ81FMW) Connecting with token ending: 6d36
info: [SOCKET-MANAGER] (E02TKJ81FMW) Changing from prov_connect to prov_connecting
info: [SOCKET-MANAGER] (E02TKJ81FMW) will stay in prov_connecting state for up to 35000 ms
warn: SOCKET-MANAGER (E02TKJ81FMW) Socket was closed because #1006: generic error
info: [SOCKET-MANAGER] (E02TKJ81FMW) Changing from prov_connecting to error
info: [SOCKET-MANAGER] (E02TKJ81FMW) will stay in error state for up to 10000 ms
info: [SOCKET-MANAGER] (E02TKJ81FMW) Changing from error to wait_for_rate_limit
Any ideas where I should be looking to fix this?