-
Notifications
You must be signed in to change notification settings - Fork 100
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
Can I configure HTTPS for Telegram webhooks? #50
Comments
I've tested the library on Heroku and GAE (long time ago) and the https web hook worked just fine. I usually test it locally using ngrok (also https). |
I can write a quick example for you but I need to know more about you configuration... |
@mukel Hi. Thank you for paying attention to this. I will come a but later with more details. |
Hi @mukel. In your code I see no place where you are configuring SSLContext as it is described in Server-Side HTTPS Support
I am uploading custom Thank you! |
I am running my bot locally, but I am forwarding port(8443) from Google Cloud Instance to local machine. |
Check #40, @greatbalin fixed the custom certificates, also check the official guide Using self-signed certificates on how the generate them (just in case you missed something). AFAIK, you don't need to deal with SSL contexts at all, as soon as you have your certificate registered in the trusted Java keystore it should work. Relevant SO thread (Option 1). The way I test locally relies on the third-party/proxy certificate, e.g. Cloudflare or ngrok, or even Google Cloud's certificate in your case. Please try adding your certificate to the trusted Java keystore, and ping me back. |
@mukel Thank you for instructions. Currently, I am using ngrok for testing purposes. |
Ping. Did it solve your issue? |
Hello @mukel. If I set certificate like this: It means that bot(akka-server) can be used directly for WebHook from telegram servers, instead of using ngrok? Yes, I use ngrok and it's work fine, but I have VDS and want use it as a https destination. |
I can't see any place where we configure HTTPS in telegrambot4s..
As a result we can see that telegrambot4s is served in HTTP:
The text was updated successfully, but these errors were encountered: