1
cavh2005
Apache on port 8081
  • 2005/10/6 21:31

  • cavh2005

  • Just popping in

  • Posts: 13

  • Since: 2005/2/2 1


Dear All

I am running Xsas on a Windows 2003 Server box. I have previously run my website, using Xsas, on a Windows 2000 box with no problems. However, on the Win2003 box I cannot run Apache on port 80 as that port is already in use. I have edited the httpd.conf file as follows:

(1) set the Listen directive so that Apache listens on port 8081
(2) added a VirtualHost directive as follows:

DocumentRoot "/www/"

(I know that this DocumentRoot is fine, because it worked okay on the Win2000 box).

Apache starts fine on port 8081, but the links on my site (which are links to other sections of the site, not links to external resources) don't work and the images are not found. I need some way of forcing all requests to have ':8081' added to them. I have trawled through the Apache documentation on Apache.org and even tried getting my head around mod_rewrite, without success. Can anyone point me in the right direction, please?

2
gediminasbyt
Re: Apache on port 8081

Don't know how exactly Apache works on Windows, but I'd guess you have to restart apache every time you do any change in httpd.conf

Also Windows2003 is very strict about who can/can't get to the box. Have you checked system logs? Does it allow redirect to non standard port like 8081?

What about IIS is it not conflicting with port 8081?

Most of the time people try to run on port 8080.


Check your system logs, IIS logs and Apache logs.

Gediminas

3
Grizzlydk
Re: Apache on port 8081
  • 2005/10/6 22:32

  • Grizzlydk

  • Just popping in

  • Posts: 68

  • Since: 2005/2/24


Hi cavh2005

Yes your virtual root is just fine.....

I,m currently looking into a simular problem, when i have the time. The port 80 is the standard on the net for webservers, what brings me back to my idea.

Maybe we can add a port number in the dns....i haven't tried yet or maybe even better (depends on your network hardware) use a port forwarding function.

Grizzly
Danish is viery iasy to spoke

4
gediminasbyt
Re: Apache on port 8081

DNS has nothing to do with in this case. When you enter an address you enter http://localhost:8081/

Gediminas

5
gediminasbyt
Re: Apache on port 8081

DocumentRoot "/www/"

I assume it's XOOPS install there, right? Change your mainfile.php config to http://localhost:8081


Maybe this will help.

And update all modules (to be safe) some use hard coded links.
Gediminas

6
Grizzlydk
Re: Apache on port 8081
  • 2005/10/6 22:54

  • Grizzlydk

  • Just popping in

  • Posts: 68

  • Since: 2005/2/24


Well...you are probally right there gediminasbyt...

Funny though...ain't localhost a "private" DNS ??? if it weren't it should it be http://mylocalip:8081...but nevermind...
Danish is viery iasy to spoke

7
gediminasbyt
Re: Apache on port 8081

@Grizzlydk

Yes you are right localhost is bound to your primary IP address and it's similar to local DNS because it's defined in your networking table.

Gediminas

8
seth_sd
Re: Apache on port 8081
  • 2005/10/6 23:15

  • seth_sd

  • Friend of XOOPS

  • Posts: 158

  • Since: 2004/11/9


Quote:
I am running Xsas on a Windows 2003 Server box. I have previously run my website, using Xsas, on a Windows 2000 box with no problems. However, on the Win2003 box I cannot run Apache on port 80 as that port is already in use. I have edited the httpd.conf file as follows:


Why not stop the service that is running on 80 so Apache can run on 80?

http://www.sysinternals.com/Files/TcpView.zip is a nice tool to find out what it is if you don't know. Maybe you do know but don't want to stop it in which case you can ignore my suggestion?
"Why can't we have a car powered on a mixture of patchouli oil, ignorance, and double standards? There seems to be an inexhaustible supply of that sh1t." - LR

9
JMorris
Re: Apache on port 8081
  • 2005/10/7 0:53

  • JMorris

  • XOOPS is my life!

  • Posts: 2722

  • Since: 2004/4/11


If you don't intent to free up port 80 (maybe using it for Remote Desktop or something), you could try editing mainfile.php so that

// XOOPS Virtual Path (URL)
    // Virtual path to your main XOOPS directory WITHOUT trailing slash
    // Example: define('XOOPS_URL', 'http://localhost');
    
define('XOOPS_URL''http://localhost');


...is changed to

// XOOPS Virtual Path (URL)
    // Virtual path to your main XOOPS directory WITHOUT trailing slash
    // Example: define('XOOPS_URL', 'http://localhost:8081');
    
define('XOOPS_URL''http://localhost:8081');


Since XOOPS looks to mainfile.php for your URL, this *should* work.

Best Regards,

James
Insanity can be defined as "doing the same thing over and over and expecting different results."

Stupidity is not a crime. Therefore, you are free to go.

10
gediminasbyt
Re: Apache on port 8081

I would never use port 80 for remoteDesktop because it's so easy to set RemoteDesktop to use another port and nobody uses remote desktop overport 80. Sincerely, I do believe we worry about it more than cavh2005 does. It's just a test box.

Although all answers were probably given already by now, question is how to use them properly.

Gediminas

Login

Who's Online

419 user(s) are online (358 user(s) are browsing Support Forums)


Members: 0


Guests: 419


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits