-
-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature request: option to send certificate for NGINX ssl client verification #85
Comments
Yeah, this could be done. |
I suspect my problem is identical
Though I can see client's calls to the docker server like I am not sure how to investigate further (eg. which logfiles in the docker, or how to check if the websocket is working?) |
@MoonCactus have you tried sending a message with a higher priority? See https://github.com/gotify/android#message-priorities |
Thanks, yes! |
(actually, the more I think about it the more I think I am polluting the initial report anyway, sorry!) |
PEBCAC? Today I deleted all my users all the app tokens, then created them again from scratch -- and it worked immediately. I also was not able to reproduce the problem! Just in case you wanted to know or it happended again: I was properly logged with the same user on the desktop and on the smartphone. When I posted a notification with curl, I was notified on the desktop, but never on the smartphone. I checked that the websockets were established on the server, and the log in the smartphone app showed no error either. It may be that I deleted/re-created the tokens more than once. Note that this probably does not close the original FR though -- I was offtopic, sorry again for that! |
I am using Gotify in combination with NGINX (based on the example configuration script). I would like to use the NGINX ssl client verification option (syntax:
ssl_client_certificate file; ssl_verify_client on
), which would require the Gotify app to send a pre-configured client certificate. Could this feature be added, or is there another/better way to do this?The text was updated successfully, but these errors were encountered: