Forum Discussion
HTTP Server Test Page
This page is used to test the proper operation of an HTTP server after it has been installed on a Rocky Linux system. If you can read this page, it means that the software is working correctly.
Just visiting?
This website you are visiting is either experiencing problems or could be going through maintenance.
If you would like the let the administrators of this website know that you've seen this page instead of the page you've expected, you should send them an email. In general, mail sent to the name "webmaster" and directed to the website's domain should reach the appropriate person.
The most common email address to send to is: "webmaster@example.com"
Note:
The Rocky Linux distribution is a stable and reproduceable platform based on the sources of Red Hat Enterprise Linux (RHEL). With this in mind, please understand that:
- Neither the Rocky Linux Project nor the Rocky Enterprise Software Foundation have anything to do with this website or its content.
- The Rocky Linux Project nor the RESF have "hacked" this webserver: This test page is included with the distribution.
For more information about Rocky Linux, please visit the Rocky Linux website.
I am the admin, what do I do?
You may now add content to the webroot directory for your software.
For systems using the Apache Webserver: You can add content to the directory /var/www/html/
. Until you do so, people visiting your website will see this page. If you would like this page to not be shown, follow the instructions in: /etc/httpd/conf.d/welcome.conf
.
For systems using Nginx: You can add your content in a location of your choice and edit the root
configuration directive in /etc/nginx/nginx.conf
.
Apache™ is a registered trademark of the Apache Software Foundation in the United States and/or other countries.
NGINX™ is a registered trademark of F5 Networks, Inc..
This is what comes up when I put in the IP address you provided
- WiderMouthOpen2 years agoEsteemed Contributor II
Run a tracert to 1sttix.org from CMD and paste the results here. See here for instructions, assuming you are running Windows 10.
- Darkatt2 years agoHonored Contributor
Just saw the traceroute, you are able to ping all the way through, so the web server you are accessing is blocking your access. That's the ONLY thing that can cause what's taking place. The traceroute shows you get ALL the way through.
FYI, you should not copy the 1st 2 hops, and that includes your WAN IP and you don't want to broadcast that.
- AK23562 years agoNew Contributor II
So 1st tix is blocking my access?
- AK23562 years agoNew Contributor II
Thank you for the advice on the WAN
- WiderMouthOpen2 years agoEsteemed Contributor II
Whatcha talkin bout Willis? A IPv4 tracert doesn't show your WAN IP. It shows the 10.x.x.x IP that Cox routes through. I always wondered why you cut your trace off at the beginning. I would show my tracert but I am on FIOS. Here is a trace from a site for comparison. Looks like it is in Detroit.
BTW I didn't see OP's trace. Did they edit/delete it?
1 172.17.0.1 0.0% 0.17ms
2 10.206.5.139 0.0% 0.29ms
3 10.206.35.8 0.0% 0.41ms
4 10.206.32.1 0.0% 3.79ms
5 lo0-0.gw1.cjj1.us.linode.com
173.255.239.101AKAMAI-LINODE-AP Akamai Connected Cloud, SG 173.255.239.0/24 0.0% 1.52ms
6 ae37.r02.lga01.ien.netarch.akamai.com
23.203.156.50AKAMAI-ASN1, NL 23.203.156.0/24 0.0% 1.96ms
7 ???
8 ae1.8.bar4.Detroit1.level3.net
4.69.217.98LEVEL3, US 4.0.0.0/9 0.0% 20.77ms
9 PATH-NETWOR.bar4.Detroit1.Level3.net
4.7.113.130LEVEL3, US 4.0.0.0/9 0.0% 20.12ms
10 dtw-elf1-po1.mojohost.com
104.193.123.247MOJOHOST, US 104.193.120.0/22 0.0% 20.13ms
11 turbo.hosthead.com
208.74.148.209MOJOHOST, US 208.74.148.0/22 0.0% 17.12ms - Darkatt2 years agoHonored Contributor
yeah, my tracert, shows my 192 address, the wan address from the router, the modem address, then the rest, so I cut out the important ones.
1 2 ms 1 ms 1 ms 192.168.x.x
2 10 ms 10 ms 1 ms 70.161.x.x
3 9 ms 11 ms 3 ms 10.15.96.1
4 12 ms 10 ms 10 ms 100.127.40.236 - WiderMouthOpen2 years agoEsteemed Contributor II
That is weird. I really thought the 2nd hop was the ethernet side of the local CMTS and should be a 10.x.x.x IP like in the 3rd hop. Has it always been this way for you? Here is my trace for comparison. My IP is similar but NOT 100.40.77.1.
1 <1 ms <1 ms <1 ms RT-AX86U-22F8 [192.168.50.1]
2 5 ms 3 ms 3 ms lo0-100.PRVDRI-VFTTP-304.verizon-gni.net [100.40.77.1]
3 4 ms 3 ms 3 ms B3304.PRVDRI-LCR-21.verizon-gni.net [100.41.129.50]Either way, why block the last 2 octets of your 192 IP address? You consider that private? I will have to take this into consideration when asking for a tracert from now on. However seeing the first 2 hops is important for checking for double NAT.
- Darkatt2 years agoHonored Contributor
Just a precaution. I used to work AIS security years ago for the Military, certain habits are hard to break.
Related Content
- 5 months ago