logo
Apache Lounge
Webmasters

 

About Forum Index Downloads Search Register Log in RSS X


Keep Server Online

If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.

or

Bitcoin

A donation makes a contribution towards the costs, the time and effort that's going in this site and building.

Thank You! Steffen

Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
Post new topic   Forum Index -> Apache View previous topic :: View next topic
Reply to topic   Topic: Connecting to Website Gives White Screen
Author
forestman11



Joined: 14 Mar 2015
Posts: 5
Location: United States

PostPosted: Sat 14 Mar '15 20:20    Post subject: Connecting to Website Gives White Screen Reply with quote

So, let me start off by saying I am completely new to website and FTP server hosting. I've hosted game servers in the past so I know about port forwarding and the like but this is obviously a step-up. I've managed to get a fully-functioning FTP server that works great on the domain I'm using but the website using Apache just gives people a blank white screen (as stated in the description). I'm using port 55567 for the website as I don't know want to use 80 because of security risks and what not. The domain being used is delawaretexasrepository.t28.net. Below are the error.log, httpd.conf and httpd-vhosts.conf. Thanks for any help!

httpd-vhosts.conf: http://pastebin.com/aWZGrrmw

httpd.conf: http://pastebin.com/4THD9Huu

error.log: http://pastebin.com/SDPkAJx7
Back to top
James Blond
Moderator


Joined: 19 Jan 2006
Posts: 7373
Location: Germany, Next to Hamburg

PostPosted: Mon 16 Mar '15 12:59    Post subject: Reply with quote

Your blank screen is a 404. (at least in my browser) Did you define the DirectoryIndex correctly?
Back to top
glsmith
Moderator


Joined: 16 Oct 2007
Posts: 2268
Location: Sun Diego, USA

PostPosted: Mon 16 Mar '15 22:37    Post subject: Reply with quote

Oddly, httpd.conf says
Listen 55567

httpd-vhosts.conf says
<VirtualHost *:80>

404 from http://domainname
403 forbidden from http://domainname:55567

Both seem strange since Indexes is allowed, so even if the index.html file was not there we should be getting a file listing. The AllowOverride is none, so no .htaccess file should be getting in the way.

Which post are you trying to run on. 55567 or 80, or both?
Back to top
forestman11



Joined: 14 Mar 2015
Posts: 5
Location: United States

PostPosted: Tue 17 Mar '15 4:16    Post subject: Reply with quote

James Blond wrote:
Your blank screen is a 404. (at least in my browser) Did you define the DirectoryIndex correctly?


I'm not exactly sure the process of this, can you explain it.
Back to top
forestman11



Joined: 14 Mar 2015
Posts: 5
Location: United States

PostPosted: Tue 17 Mar '15 4:17    Post subject: Reply with quote

The website is being run through a dynamic DNS which is using port 80 and then to my computer which is 55567.
Back to top
glsmith
Moderator


Joined: 16 Oct 2007
Posts: 2268
Location: Sun Diego, USA

PostPosted: Tue 17 Mar '15 10:33    Post subject: Reply with quote

No, actually the dynamic dns (afraid.org) is on port 53, that is the port dns servers run on. Read up on how dns works if you do not understand this.

That said, I'm pretty sure I know what is going on now. Your ISP seems to be Comcast, at least the IP your domain points to is a Comcast IP and I believe Comcast is blocking port 80 right?

Here is what I see if I go to your IP (not domain name) on port 55567, I get these response headers that look correct.
HTTP/1.1 403 Forbidden
Date: Tue, 17 Mar 2015 06:36:41 GMT
Server: Apache/2.4.12 (Win32)


If I go to your IP on port 80 all I get back is;
HTTP/1.0 404 Not Found

The later here I think is Comcast intercepting the request. If it was your server there should be more than this and it would most likely answer HTTP/1.1 404 Not Found, not HTTP/1.0 and there would be more headers also.

Because of that, you will have to go to your website via a URL of http://yourdomain:55567 like it or not. [1]

Now, your config problems, some of which I've just noticed. In httpd.conf you have;
DocumentRoot "G:/Webservers/Apache24/htdocs"
<Directory "c:/Apache24/htdocs">
Those two need to match, this is why I'm getting a 403 Forbidden when going to just your IP.

Now your VHost. If you are only going to have just one site on your server you really do not need to use Virtual Hosts. If you plan to have more than one, then you will need to do a couple things.

First, change the *:80 to *:55567, your server will never ever receive a request on port 80 with the block.

Second, since your DocumentRoot for your Vhost is different than the one in httpd.conf, you will need to adhere to the "Main host goes away" section in the docs http://httpd.apache.org/docs/2.4/vhosts/name-based.html

I see they have reworded it to make it more understandable, maybe, but it basically says that your first Vhost must be this.
Code:
<VirtualHost _default_:55567>
DocumentRoot G:/Webservers/Apache24/htdocs
</VirtualHost>


Yes, that is the same DocumentRoot as what is in httpd.conf. That now become the default host, so any request your server receives that does not correspond to any configured Vhosts's will be land at that DocumentRoot.

Now your VHost, because your DocumentRoot is not the same or even below the one you have in httpd.conf, you will need an entire <Directory>...</Directory> container for it as well, or your Vhost will then 403.

[1] You could have Web Forward at Afrail.org point to your domain like;
http://differentdomain -> http://yourdomain:55567
Back to top
forestman11



Joined: 14 Mar 2015
Posts: 5
Location: United States

PostPosted: Wed 18 Mar '15 17:24    Post subject: Reply with quote

So, change the VHost port to 53? Or how do I use it without VHost. Also, I do not think that Comcast blocks port 80 but maybe. Now, besides the config problems, could I not forward the Dynamic DNS server to my IP on port 55567?
Back to top
James Blond
Moderator


Joined: 19 Jan 2006
Posts: 7373
Location: Germany, Next to Hamburg

PostPosted: Wed 18 Mar '15 18:09    Post subject: Reply with quote

Nope, port 53 is for DNS requests. the vhost as glsmith posted needs to be 55567
Back to top
forestman11



Joined: 14 Mar 2015
Posts: 5
Location: United States

PostPosted: Wed 18 Mar '15 18:43    Post subject: Reply with quote

James Blond wrote:
Nope, port 53 is for DNS requests. the vhost as glsmith posted needs to be 55567


I will try that when I get back to the house. But what about my other suggestion? Will that work?
Back to top


Reply to topic   Topic: Connecting to Website Gives White Screen View previous topic :: View next topic
Post new topic   Forum Index -> Apache