Unable to verify subscriber endpoints

[dlemmink]

Following the instructions here: https://dev.fitbit.com/build/reference/web-api/developer-guide/using-subscriptions/#Configuring-a-Su... I created an endpoint to service the Fitbit subscriptions and created the logic to return the correct status with the verify codes provided, yet the subscription cannot be verified nor am I seeing any hits on my webserver.

It is visible to the public.  It appears to be returning the correct status codes.  I've read that Fitbit has issues with some certificates.  Could that be my issue?

[Gordon-C]

Hi @dlemmink 

I'm going to send you an email to get some additional information from you which will help confirm what the problem might be.

Gordon

[JonasSevenD]

I'm experiencing the same problem. There are no request arriving on our server after pressing the 'Verify' button.
I also read about the issues with SNI when running multiple subdomains on the same IP. So i tried setting a default_server in Nginx, but still there are no requests arriving.

If possible, I would like to avoid getting a dedicated IP. Assuming that SNI is actually the problem.

[dlemmink]

I had an issue where Fitbit was not honoring my wildcard domain certificates. I change certificate providers and it magically worked. I was using a wildcard domain certificate.