I removed my ssl options in apache for one of my websites and I changed the port for virtualhost back to 80. I also remove the certificates for feedmebits.nl. I restarted apache but now my website one seem to come online anymore. My other website wors fine, when I try to go to feedmebits.nl via a proxy, I get the following error: Couldn't connect to feedmebits.nl:443: No route to host . Seems like somewhere it's still trying to connect to the ssl port. I've been search and looking over my apache config file. Can't find anything there and I there's nothing installed anymore that has to do with ssl. Any advice to help me in the right direction. My website access.log shows that I did try to connect via a proxy:
69.175.115.50 - - [18/Jan/2012:10:55:51 +0100] "GET / HTTP/1.0" 303 - "http://www.mywebtunnel.com/" "Mozilla/5.0 (Windows NT 5.1; rv:9.0.1) Gecko/20100101 Firefox/9.0.1"
but it won't display my site.
I tried remove all SSL certificated stored in IE and in firefox cuz I saw it still had the certificated stored there. But removing them didn't help either.
Are you connecting using http:// or https:// ...? Don't forget the browser may sometimes cache info!
Quote:Are you connecting using http:// or https:// ...? Don't forget the browser may sometimes cache info!
I also cleared the browser cache. using http://
Could just be an issue with that proxy you're going through, so something outside of your control.
FWIW, I can't get to
http://feedmebits.nl:80 either. I was given a cookie from your site, but then no content came up (you should see the connection from my home server, orac).
Check you haven't got the SSL engine still enabled for this site. Also, feel free to post your config file here and we can check it out.
Code:
ip- - [18/Jan/2012:20:00:27 +0100] "GET / HTTP/1.1" 303 - "https://www.linux-noob.com/forums/index.php?/topic/4268-apachemod-ssl-problem/page__pid__15864" "Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Red Hat/3.6.24-3.el6_1 Firefox/3.6.24"
Yeah I think I see it. This last one right. I don't have the SSL engine enabled for the site under apache:
Code:
<VirtualHost 62.212.66.15:80>
ServerName feedmebits.nl
ServerAdmin admin@feedmebits.nl
DocumentRoot /home/www/feedmebits.nl/htdocs
ErrorLog /home/www/feedmebits.nl/logs/error.log
CustomLog /home/www/feedmebits.nl/logs/access.log combined
<Directory /home/www/feedmebits.nl/htdocs>
AllowOverride None
order allow,deny
allow from all
Options -Indexes
DirectoryIndex index.php
</Directory>
</VirtualHost>
<VirtualHost 62.212.66.15:80>
ServerName vanderrijst.eu
ServerAdmin admin@vanderrijst.eu
DocumentRoot /home/www/vanderrijst.eu/htdocs
ErrorLog /home/www/vanderrijst.eu/logs/error.log
CustomLog /home/www/vanderrijst.eu/logs/access.log combined
<Directory /home/www/vanderrijst.eu/htdocs>
AllowOverride None
order allow,deny
allow from all
Options -Indexes
DirectoryIndex index.php
</Directory>
</VirtualHost>
I removed all the SSL Engine options. But I may just be overlooking something. But if I had a wrong config in apache or somewhere else. My other site shouldn't be working either. So it has to be something with the one site that I'm overlooking.
The 303 suggests that Apache is trying to bounce it (redirect) elsewhere. You running mod_redirect or mod_rewrite?
Also, can you access a different (new) file in that dir rather than the index?
Quote:The 303 suggests that Apache is trying to bounce it (redirect) elsewhere. You running mod_redirect or mod_rewrite?
Also, can you access a different (new) file in that dir rather than the index?
I made a test file named "test.htm with a basic html format in it. and when I do
http://feedmebits.nl/test.htm it displays.
I changed the DirectoryIndex to test.htm and it works and when I have set as index.php it also works.
I don't have mod_redirect or mod_rewrite running.
I also tried seeing if my index file was corrupt. by copying my other index file from my other site to feedmebits.nl. but then my test file didn't even work anymore. So I restored it.
Okay... it looks like a caching problem somewhere along the line, and possibly something you may not be able to control higher up.
Another factor to consider is any of your TTL values set in Apache or the web page itself - they usually inform cache functions (browser, proxy etc) how long a page should be cached for.
I tend to use CTRL+REFRESH (or is it shift+refresh?) to bypass the local cache and force a refresh hit.
I can't remember setting up any TTL values in my config file, I know the term but haven't worked with it before.. I searched through my config file though, nothing. I'm at work now and I tried ipconfig /flushdns
under windows. Didn't help either. But since I am able to get to my test file, I would think it can't be a problem on my server or else I wouldn't be able to reach my whole site and wouldn't be able to reach my other site either. But if it's a cache problem higher up? How can I figure out what it is?
I am getting a connection looking at my access logs:
- - [19/Jan/2012:13:54:50 +0100] "GET / HTTP/1.1" 303 - "-" "Mozilla/5.0 (Windows NT 5.1; rv:9.0.1) Gecko/20100101 Firefox/9.0.1"
I'll try and search on httpd 303 error