I have Sharetribe open source installation with custom landing page deployed to DigitalOcean with Ubuntu 16.04 and Nginx/passenger web server.
The sites works on HTTP but not on HTTPS. I have Let’s Encrypt certs configured and working. When I have HTTPS enabled, the landing page works but none of the links on the header like “Register” or “Log in”, I just get 404 page not found error after clicking a link. If I use HTTP instead then everything works fine.
I have added the domain to communities table and use_domain is true. What else I need to do to get the site working on HTTPS?
I use different domains for HTTP and HTTPS for testing purposes. As I switch to HTTP I update communities table accordingly.
This kind of behavior doesn’t sound familiar to me…
By default the protocol shouldn’t cause 404 errors… Can you check if the 404 is returned by the Rails application, or possibly some other server component?
There is a config variable “always_use_ssl” that could be related, but I think it shouldn’t affect this case, but you can try modifying that, and see if any effect.
Running on separate domains for different protocols sounds like a setup that might cause the issue one way or another, so if it is possible to test running both on same domain, it could be one way of debugging this.
Also if you get logging out of the rails app when requests come in and cause 404 that might help to pinpoint where and what is “not found” when 404 is returned.