Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Can no longer force non-https schemes in custom server picker
See original GitHub issuefor localhost dev this is important. Should be able to change the server on the login page to http://localhost:port without issue. Workaround is to use a local element with config.json
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Enabling HTTPS on Your Servers - web.dev
If you are not sure whether you can fully deploy HTTPS yet, forcing your site to use HTTPS for all sub-resources may backfire....
Read more >Force HTTPS with .htaccess for Security | InMotion Hosting
Force HTTPS connections with the .htaccess to make sure every connection is a secure one. Your website's visitors should be accessing your ...
Read more >In Nginx, how can I rewrite all http requests to https while ...
The problem occurs when a POST request is made to your server. If the server response with a plain 30x redirect the POST...
Read more >Flask url_for generating http URL instead of https
It seems that you're trying to partially enforce HTTPS for only a few "secure" routes, but you can't ensure that your https-URL is...
Read more >The Complete Guide To Switching From HTTP To HTTPS
HTTPS ensures that the website can't be modified. ... methods to enable on the server, is the Mozilla SSL Configuration Generator, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The fix is due to go out on Monday - we close issues ahead of the formal release.
I can confirm this is working again. Thank you for the quick fix @t3chguy!