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
{{ message }}
This repository has been archived by the owner on Feb 24, 2024. It is now read-only.
When I started my app in production, it said it was listening at http://0.0.0.0:3000 -- that's not what I wanted! When I visited the site, everything worked fine, including the TLS (and redirect from 80 to 443). Port 3000 was not open. So the log message was wrong.
Thanks for filing an issue and the PR for it. Indeed, the information is not correct, and I am considering what could be the best solution. I will review your PR soon and will reply.
Description
Today, I deployed my Buffalo application. I had written some TLS code that integrates it with autocert (Let's Encrypt). Basically, I copied this code: https://gist.github.com/hdm/d271eb94a51f7f908ecb9ddc82d2b644
When I started my app in production, it said it was listening at http://0.0.0.0:3000 -- that's not what I wanted! When I visited the site, everything worked fine, including the TLS (and redirect from 80 to 443). Port 3000 was not open. So the log message was wrong.
I saw this FIXME:
buffalo/server.go
Lines 25 to 27 in 215a8f9
It seems pretty straightforward; one could just display the endpoint as it's running rather than blindly copying from the configuration.
I've already solved this problem on my fork, so I'll open a PR in a sec after I make sure nothing is broken.
The text was updated successfully, but these errors were encountered: