Notices tagged with nginx
-
drak (drak)'s status on Friday, 04-Feb-2022 13:53:39 EST 
drak
#letsencrypt via #nginx: https://www.nginx.com/blog/using-free-ssltls-certificates-from-lets-encrypt-with-nginx/ — that was surprisingly easy -
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1)'s status on Saturday, 23-May-2020 22:47:15 EDT 
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
@clacke@libranet.de I mostly knew this already, but it is more a comment about how often I see it with #Nginx (almost never with #IIS or #Apache). -
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1)'s status on Saturday, 23-May-2020 12:19:08 EDT
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
Oh, #nginx, why is such a common screen? What could this message mean (about the way people configure Nginx)? https://nu.federati.net/attachment/269859 -
Douglas A. Whitfield (musicman)'s status on Tuesday, 19-May-2020 17:22:41 EDT 
Douglas A. Whitfield
#TIL: Angular's web-server doesn't deal with networking like #nginx or #apachehttpd (both of which work fine on test server).
I learned that working on https://github.com/Faldrian/bandcamp-scraper
I also learned that #CouchDB is a PITA. I probably could have figured it out, but it isn't high on the "must learn" list. -
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1)'s status on Tuesday, 14-Jan-2020 19:15:04 EST
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
@musicman That’s awfully specific. There might be podcasts focused on webservers ( #Apache #httpd, #Lighttpd, #Nginx, #Cherokee, #OpenBSD httpd, etc ) and plugins / extensions ... maybe with some coverage of Web APIs and such. Or there might be some that cover everything the Apache org produces.
I’m not confident that you will find any #podcasts that cover only the intersection. -
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1)'s status on Sunday, 22-Dec-2019 00:55:28 EST
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
Soykaf is getting the #Nginx 502 Bad Gateway error message right now. Not gonna check Pleroma tonight. -
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1)'s status on Thursday, 12-Dec-2019 13:32:56 EST
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
@geniusmusing Perhaps F5 is getting some big contracts with their proprietary server. (I presume it is built atop the FOSS version of #Nginx.) Or maybe Rambler plans to mirror the SCO "stolen IP" argument in an attempt to close source the product. -
Guillaume (postblue)'s status on Thursday, 15-Aug-2019 07:48:57 EDT 
Guillaume
How to configure x-static-delivery in !gnusocial with #nginx? Getting 404 on thumbnails https://notabug.org/diogo/gnu-social/issues/54 -
Chimo (chimo)'s status on Tuesday, 26-Jan-2016 14:42:58 EST 
Chimo
#nginx security advisory (regarding "resolver" directive) http://mailman.nginx.org/pipermail/nginx/2016-January/049700.html -
MMN-o ✅⃠ (mmn)'s status on Wednesday, 30-Dec-2015 21:41:47 EST 
MMN-o ✅⃠
Hey @nybill, you don't have fancy URLs enabled :O So everything has to be prefixed with "/index.php/". That causes problems with discovery. Of course it should be handled better, but I think that might be one source of problems. I don't think you should fix this by enabling fancy URLs directly (that could cause other issues with at least !sn, probably !gnusocial too, … -
lnxw48 (Linux Walt) (lnxw48)'s status on Saturday, 05-Dec-2015 10:37:54 EST 
lnxw48 (Linux Walt)
@mmn I was thinking of filing a bug suggesting that fancy URLs should be required. Maybe some #nginx users would like to document how to make that work. Also, any decent host allows using subdomains, so !gnusocial should be installed in the root of the [sub]domain. -
lnxw48 (Linux Walt) (lnxw48)'s status on Saturday, 05-Dec-2015 10:37:54 EST
lnxw48 (Linux Walt)
@mmn I was thinking of filing a bug suggesting that fancy URLs should be required. Maybe some #nginx users would like to document how to make that work. Also, any decent host allows using subdomains, so !gnusocial should be installed in the root of the [sub]domain. -
Chimo (chimo)'s status on Monday, 20-Jul-2015 23:34:18 EDT
Chimo
also, #noteToSelf #nginx !gs !hackfest https://github.com/chimo/nginx-configs/blob/master/conf.d/sn.conf#L39 -
MMN-o ✅⃠ (mmn)'s status on Tuesday, 31-Mar-2015 10:46:38 EDT
MMN-o ✅⃠
@mmn @andstatus ...and even the #nginx "solution" looks like a dirty hack. "on error, go to a page that doesn't treat it as an error!". HTTP/1.1 describes "411 Length Required" as "The request did not specify the length of its content, which is required by the requested resource". If the resource requires it - the solution is not to add a hack on the resource side but … -
lnxw48 (Linux Walt) (lnxw48)'s status on Thursday, 22-Jan-2015 16:36:30 EST
lnxw48 (Linux Walt)
By the way, if you’re thinking about running !sn / !gnusocial on #lighttpd, the included
lighttpd.conf.examplefile makes it very easy to get things running. #nginx, #cherokee, #hiawatha users should contribute similar files, to make it even easier to !selfhost. -
MMN-o ✅⃠ (mmn)'s status on Wednesday, 21-Jan-2015 17:21:48 EST
MMN-o ✅⃠
Works for me, @knuthollund! Btw, your #nginx should be configured to host each separate vhost over #HTTPS too. (right now it serves the q. subdomain for https://kollektivet0x242.no/ :] - with just HTTP it works as it should) -
pztrn (pztrn)'s status on Thursday, 14-Aug-2014 23:54:21 EDT 
pztrn
!tzag, !fediverse. While !coffee making itself, it's time to make a load-balancer with #nginx help for sites at work.
All Hacker Poesy content and data are available under the