Can a room owner/mod remove the outdated starred "Can a room owner/mod remove the outdated starred "Can a room owner/mod remove the outdated starred "AIM v0.7 is available..." please?" please?" and the outdated starred "Can a room owner/mod remove the outdated starred "AIM v0.7 is available..." please?" please?
Can a room owner/mod remove the outdated starred "Can a room owner/mod remove the outdated starred "Can a room owner/mod remove the outdated starred "AIM v0.7 is available..." please?" please?" and the outdated starred "Can a room owner/mod remove the outdated starred "AIM v0.7 is available..." please?" please?
[ SmokeDetector | MS ] URL-only title, bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: supplement4help.com/alpha-force-testo/ by pwj on askubuntu.com (@ThomasWard)
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, repeated URL at end of long post: Hl Slim Pro components list? by jordnt on arduino.SE
@YvetteColomb tl;dr We adjusted the minimum accuracy requirement on autoflagging; you just need to change the minimum weight on https://metasmoke.erwaysoftware.com/flagging/conditions/26/edit to a larger number (and tick the 'flags enabled' box). 175 is enough to get by.
or depending on where that 'system' sits / is configured
on my home network I have a box in my DMZ that all 80/443 requests get sent to
that runs an nginx reverse proxy for different other boxes, handling what goes to which systems internal
then passes it to those systems, and acts as the 'proxy' into the network for that website/service being requested
for instance, gitlab.hellnet.io on HTTPS will go to 'webrouter', which then passes into the Server VLAN for that GitLab server, and then traffic goes back out the same way
i only have the one IP on my home net so :P
(several VPSes have the same setup, and at my workplace a Docker-container-running server has nginx on it, listening for certain internal domains in order to reverse-proxy to the Docker instances for web services too)
i kinda stole our travis and circle configs for Smokey and adapted to my needs.
@ArtOfCode the nginx process listens on 0.0.0.0:80 for all those requests, and handles them based on whether requested host matches server_name or not
it doesn't spawn two separate servers, it's just saying "Both of these will listen on the same IP/Port combination", but this only works for just '80' without an IP, otherwise it can break things
@ThomasWard oh, so I actually only have one thing on port 80 - nginx. The two web servers run on some other local port, and nginx fires requests to them based on the Host header? Kinda like (or exactly like) a vhost setup.
just how my web router on 10.255.50.1 can route to 10.255.100.10 (gitlab) or 10.100.75.18 (my nessus system, which is allowed to receive from 10.255.50.1 and only that across DMZ->nonDMZ)
it's actually pretty transparent in terms of how things're handled
if you have a billion sites, yeah, but in reality it's not too much different from standard websites
@ArtOfCode Especially useful when you have everything on one computer, imagine Docker containers on a specific system, which all run in the local-system NAT'd setup
you can't get to those Docker containers but all of them running listen for websites, and need to be reached by the LAN
or the Internet if on an internet facing server
so, nginx on the 'host', handling the passoff based on host to the individual containers
which would be listening on a localhost-bound or similar higher-number port
there's a lot of other good use cases too, i'm just too lazy to write them out :)
Job for nginx.service failed because the control process exited with error code. See "systemctl status nginx.service" and "journalctl -xe" for details.
invoke-rc.d: initscript nginx, action "start" failed.
dpkg: error processing package nginx-core (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of nginx:
nginx depends on nginx-core (>= 1.10.0-0ubuntu0.16.04.4) | nginx-full (>= 1.10.0-0ubuntu0.16.04.4) | nginx-light (>= 1.10.0-0ubuntu0.16.04.4) | nginx-extras (>= 1.10.0-0ubuntu0.16.04.4); however:
and then sudo ln -s /etc/nginx/sites-available/catchall-default /etc/nginx/sites-enabled. and sudo systemctl restart nginx
so if any other sites are directed to your server and aren't defined in the configs, you don't serve your sites for those requested sites (happens to me all to frequently to see crap coming in), and the requestors see HTTP503 errors instead
@ArtOfCode and you're done, just use the server { ... } blocks in the original conf I wrote you as a template, adjust server_name and the port on proxy_pass, done.
@ArtOfCode fortunately the only thing left to do is the other servers :P
@ArtOfCode then run sudo apt-get install haveged; sudo openssl dhparam -out /etc/nginx/dhparam2048, and under that ssl_session_tickets line, add this: ssl_dhparam /etc/nginx/dhparam2048;
restart nginx, done.
@ArtOfCode oops hang on
add this to the add_header lines: add_header Strict-Transport-Security "max-age=63072000; includeSubdomains; preload";
so still not too hard to configure when you're spoon-fed the steps and configs :)
note that for each server you enable SSL on, you don't need to rerun the openssl dhparam stuff or that install haveged
