You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The action log contains a bit more useful info: Got an error (on error) [Error: Couldn't connect to server]. Including that in the issue would be a good start.
What would be even better is providing the actual cause of the issue, for example:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When the connection to the server fails, the issue contains:
That really doesn't give much information, see weblate-status-bot/nijel-status#3 for example.
The action log contains a bit more useful info:
Got an error (on error) [Error: Couldn't connect to server]
. Including that in the issue would be a good start.What would be even better is providing the actual cause of the issue, for example:
Using https://node-libcurl-docs.netlify.app/enums/_lib_enum_curlcode_.curlcode.html might be the way to figure out the actual reason.
I think it was a DNS issue in this particular case, but that's just my guess.
Beta Was this translation helpful? Give feedback.
All reactions