You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
The closest thing to the previous hands-off behavior I can think of is using iptables to send port 80 to some other port, and deploying an nginx config that passes that through to port 80 on self except for the well-known ACME paths. But ugh.
I guess a less ugly method would be to have the default vhost serve the ACME challenges and then having an include to add that functionality in every additional port 80 vhost. Still ugh.
That’s what I do: # Within each site config server block: include snippets/letsencrypt.conf; # letsencrypt.conf: location ~ .well-known/acme-challenge/ { root /var/www/letsencrypt; default_type text/plain; }
Yes, this is the plan. But the previous config required zero additional config stanzas (other than the cert itself).
I have a generic http vhost which only serves the acme challenges and does https redirects, nothing else - all content is in https vhosts...
Example for Apache and nginx: https://gist.github.com/TobiX/63b698db7de37ec7d09f380ea0da0a24 …
"manual http" users can continue being lazy
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
