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
Is your feature request related to a problem? Please describe.
I am trying to set up notifications to a local Gotify server. It's using http protocol and it is not exposed to the Internet.
However, scrutiny defaults to https, and connection fails.
Describe the solution you'd like
An ability to connect to the local Gotify server using http protocol.
And here are the errors I see in the logs when it tries to send notification:
scrutiny | time="2024-09-20T08:51:35Z" level=info msg="Sending notifications to gotify://10.0.0.1:8030/BsbtZ6qVwOzOdeu" type=web
scrutiny | time="2024-09-20T08:51:35Z" level=error msg="One or more errors occurred while sending notifications for gotify://10.0.0.1:8030/BsbtZ6qVwOzOdeu:" type=web
scrutiny | time="2024-09-20T08:51:35Z" level=error msg="[failed to send notification to Gotify: error sending payload: Post \"https://10.0.0.1:8030/message?token=BsbtZ6qVwOzOdeu\": http: server gave HTTP response to HTTPS client]" type=web
I also tried explicitly adding "http" to the url string, but then it starts looking like this: https://http//10.0.0.1:8030/BsbtZ6qVwOzOdeu which is wrong
Maybe I missed something and there is already a way to achieve this?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I am trying to set up notifications to a local Gotify server. It's using http protocol and it is not exposed to the Internet.
However, scrutiny defaults to https, and connection fails.
Describe the solution you'd like
An ability to connect to the local Gotify server using http protocol.
Additional context
My yaml config is like this
And here are the errors I see in the logs when it tries to send notification:
I also tried explicitly adding "http" to the url string, but then it starts looking like this:
https://http//10.0.0.1:8030/BsbtZ6qVwOzOdeu
which is wrongMaybe I missed something and there is already a way to achieve this?
The text was updated successfully, but these errors were encountered: