Other servers were having their server type placed in the results in this site: https://www.sslshopper.com/ but my server type doesn't show up in that list. Just wanted to give nginx some credit by trying to get it to show like other servers do.by battles - How to...
Results: HTTP/1.1 200 OK Server: nginx/1.2.1 Date: Wed, 06 Apr 2016 10:16:01 GMT Content-Type: text/plain Content-Length: 26 Last-Modified: Sun, 15 Jun 2014 17:24:36 GMT Connection: keep-alive Accept-Ranges: bytes User-agent: * Disallow: / Possibly the 'User-agent: *' or 'Disallow: /' forbidding its display? That is what is in my robots.txt file.by battles - How to...
Didn't have that off and tried putting it in anyway, but still didn't display.by battles - How to...
If you put anonusa.net into this ssl lookup site, it shows the 'Server type' in the listing. When I lookup my own site, the server type is not listed. Is there some parameter that you put in the config file that causes the server type to display? Here is a site that displays it: https://www.sslshopper.com/ssl-checker.html?host=mixmin.net#hostname=anonusa.net Thanksby battles - How to...
error_page 404 /404.html; location = /404.html { root /var/www/; } I use the above to catch and direct 404s to a custom 404.html page in /var/www. All my other pages are located in another place. This works fine for catching invalid file request (www.me.net/path1/invalid_file.txt), but doesn't work properly for invalid folder request (www.me.net/invalid_path/). The problem iby battles - How to...
WOW! It is so easy when you are a pro - thank you very much!by battles - How to...
I have the follow code that accesses my pages correctly: location /echolot { alias /home/webpage/www/echolot; autoindex on; } When I go to allpingers.net/echolot/, it goes to an 'Index of /echolot/' page. Where I want allpingers.net/echolot/ to actually go to is https://allpingers.net/echolot/echolot.html. I can't simlink /echoloby battles - How to...
Thanks for the pointer.by battles - How to...
I have a folder that contains multiple files that need to be accessed and displayed. I could setup a location {} for each easily enough, but this folder can have files added and deleted by a program that creates the files. I need an example of how to setup a location {} that will access the specific needed file when a link is clicked on within a list page. Here is an example of such a page: httby battles - How to...
I have the /etc/nginx/sites-available/default set up like this. The reason is because I want my personal connections to a dashboard webpage to be logged to /var/log/nginx/12.34.56.789.log. This keeps my personal connections separated from others who hit my other webpages by placing them into the separate log access_log. I seem to be having trouble with ssl connections all going to the 12.34.by battles - Other discussion
Thanks. Definitely have some more studying to do.by battles - Other discussion
I'm not real knowledgeable in this stuff. Here is a traceroute, but I can't tell anything from it. The firewall is searching for the -string vtigercrm. I thought that packets coming in with that in it would be rejected. I don't now how routing would affect that. traceroute to 69.58.178.57 (69.58.178.57), 30 hops max, 60 byte packets 1 me.me.32.254 (me.me.32.254) 0.805 ms me.me.32.253 (mby battles - Other discussion
There still seems to be a problem. My iptables -string DROP entry is now: iptables -I INPUT 1 -p tcp -m multiport --dports 80,443 -m string --string "vtigercrm" --algo bm --to 300 -j DROP Today I found this in my above example 123.456.789.012:80 log: 95.110.186.196 - - [04/Aug/2015:09:57:55 -0500] "GET /vtigercrm/test/logo/zizo.php HTTP/1.1" 404 2096 "-" &quby battles - Other discussion
Never thought about him coming in on 443. That is probably why iptables is missing the drop. He is getting into the special log because the port 443 is being hit through the first server 'listen 443 ssl'. I am not a complete newbie, but still learning. Thanks for the help.by battles - Other discussion
I have nginx setup with the following parameters in order to place entries into a different log that come from my own ISP IP. I use some iptables -string drops, all that drop correctly except for one that is listed below. They get past the iptables -string drop and are also ending up in my special log. I was wondering if someone can see anything where the nginx parameters is causing these -striby battles - Other discussion
![]() |
![]() |
![]() |
![]() |
|