Setting up HTTPS to make webhooks work

[slcpunk]

So I hate to ask, because clearly everyone knows how to do this, but I want to setup the webhooks, but I need statistics for strava to run under https instead of http.
i have some vague ideas of how to do that generally ( get SSL cert, install change http service to use https ) but not really within the framework of statistics for strava. if instructions are too much - beyond the scope - then i get it, but figured i would ask because i love the project so far. i guess i can just crank up the frequency of the sync job once my activities are up-to-date and maybe then I don't really need the webhooks, which if i understand it would just provide a more real-time synchronization.

thanks in advance,
shane

[dschoepel]

The webhooks feature is a really nice add, lots easier to keep Statistics-for-Strava up-to-date. 👍

You may want to look at setting up a proxy to do the work of redirecting HTTP to HTTPS.

Assumptions:

• Strava needs to send messages (webhooks) to your Statistics for Strava container hosted in your local network
• You have a registered domain name you own and can use for this. To set one up, here's a couple I've used: NameCheap, GoDaddy
• You have a DNS service pointing to your Internet IP for your local (home). You likely will need to set up a dynamic DNS service most ISP's don't assign a fixed (static) IP to your Internet connection. Here's a list: Dynamic DNS Providers, the free services work fine unless you have a lot of Domains to manage. This works well for me Dynu.
• Your OK (and have some experience) with exposing your local network to inbound traffic, a proxy plus firewall should provide basic level of comfort doing this.

Note: A good rule of thumb to follow is not to put all your eggs in one basket when it comes to purchasing/using tech services. Many of these services mentioned above, provide all in one Hosting, DNS, Domain Name, SSL certificates. I am suggesting that you separate these across different providers, unless there is a compelling reason Not to do so. Goal is to limit failure domains if/when there are issues.

For a relatively easy, all-in-one setup for a proxy and SSL cert generation, I would suggest SWAG - Secure Web Application Gateway. Swag runs in a docker container, they have been around for years, its opensource (free), and will generate and manage your expiring SSL cert(s) for free.

• Swag Documentation

They have a lot of sample HTTPS configs for many applications that you can use to adapt to Statistics-for-Strava. You'll need to pick one that is configured for a domain. The piwigo.subdomain.conf.sample would be a good one to copy and modify to point at your Statistics-for-Strava site.

Preset proxy confs
Our SWAG image comes with a list of preset reverse proxy confs for popular apps and services. They are hosted on Github and are pulled into the /config/nginx/proxy-confs folder as inactive sample files. To activate, one must rename a conf file to remove .sample from the filename and restart the SWAG container. Any proxy conf file in that folder with a name that matches *.subdomain.conf or *.subfolder.conf will be loaded in nginx during container start.

Hope this gives an idea of what's needed to access Statistics-for-Strava via HTTPS.