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
By default, send is using the formatted hook, like this "https://%s/hooks/%s/%s", host, tokenA, tokenB. However, in cases when my 443 port is busy with a different service, and I've set the chat service to use port 5000 or 3000, adding the port into the rawURL - it ends up with an error:
atighineanu
changed the title
In case I use a custom port for the chat service shoutrrr shows an error
In case I use a custom port for the chat service shoutrrr shows a segfault
Nov 5, 2020
piksel
changed the title
In case I use a custom port for the chat service shoutrrr shows a segfault
Rocketchat service segaults when connection to the server fails
Nov 5, 2020
This is in a way two issues in one. I renamed the issue to point to the part of it that is an actual bug/error.
The reason for why you are seeing this are (as you have figured out) that Rocketchat doesn't support specifying the port, which is more of a feature request.
simskij
changed the title
Rocketchat service segaults when connection to the server fails
Rocketchat service segfaults when connection to the server fails
Nov 15, 2020
By default, send is using the formatted hook, like this
"https://%s/hooks/%s/%s", host, tokenA, tokenB
. However, in cases when my 443 port is busy with a different service, and I've set the chat service to use port 5000 or 3000, adding the port into the rawURL - it ends up with an error:First, I've noticed there is no proper check if the posting happened without problems --> pkg/services/rocketchat/rocketchat.go:
A PR is coming right away to address the respective issue.
The text was updated successfully, but these errors were encountered: