You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got a self-signed certificate set up using the localhost gem. When I run bundle exec falcon serve, my site works fine, and I don't get a security warning in the browser.
If I run bundle exec falcon serve -b https://0.0.0.0 -p 4000, I get a security warning in the browser, even when accessing the site via https://localhost:4000.
Is there any way to easily set up a self-signed certificate so I can bind to 0.0.0.0 and still avoid the browser warning?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I've got a self-signed certificate set up using the
localhostgem. When I runbundle exec falcon serve, my site works fine, and I don't get a security warning in the browser.If I run
bundle exec falcon serve -b https://0.0.0.0 -p 4000, I get a security warning in the browser, even when accessing the site viahttps://localhost:4000.Is there any way to easily set up a self-signed certificate so I can bind to
0.0.0.0and still avoid the browser warning?Beta Was this translation helpful? Give feedback.
All reactions