Access without changing port

http://yourserveriphere/whm/

have fun.

 

Cpanel uses that as a defalt port and i dout there is a way to change it. You'll need to chane the way your program works, Or shut down cpanel temp while you use your program.

 

Get nph-proxy it works great. The url for it somewhere in this forum.

 

Here is the URL to the site for it.

http://www.jmarshall.com/tools/cgiproxy/

 

Basically that's what it does. You treat it like any other CGI script, keeping in mind that the name MUST start with nph-

you call it like http://www.domain.com/cgi-bin/nph-proxy.cgi

You enter the cpanel url http://www.domain.com:2082 and you can then access your cpanel.

 

Hate to revive this topic, but wondering if anyone is successfully using nph-proxy.

Both myself and my sysadmin have tried to get nph-proxy working with cpanel. It "works," but takes FOREVER to load. Eventually the main cpanel index page loads, but then each image takes forever to load (XSkin has a lot of images).

Server load is low, so that's not the problem. I even tried nph-proxy from a remote server running mod_perl. Same problem. Any clues?

Me and my sysadmin are about to do a good deal of debugging, but if anyone can save us the trouble, I'd appreciate it if you could let us know.

I thought this was a DNS issue of some sort, but it doesn't seem to be. I'm not sure what's slowing it down.

Thanks for any help,
Russ

 

That unfortunatly is the way it is working now.

I remember when we first set it up it was fairly quick, then at one point it just started to dog.

No resolution so far.

 

DGBaker,

Are you saying that it was quick, but then you upgraded to a newer version of nph-proxy and it got slow? Or new releases of CPanel somehow made proxying to it slow.

I'm wondering if maybe CPanel isn't sending the proper content-length header and nph-proxy is hanging waiting for more data? Just a guess.

Anyone have a solution?

Thanks,
Russ

 

I think it was around when we went to cPanel 6.0.

It is definatly cpanel related as if you use to access to say webmail on 2095 it works perfectly with virtually no lag at all.

We've also noticed that it is an issue only for 2082 and 2083, accessing 2086, 2087 work just fine.

 

Yep,

I can confirm that... Only an issue for CPanel, not WHM or WebMail. Not sure exactly what this is due to.

If I figure it out, I'll let you know.

Thanks,
Russ

 

For future reference (people searching the forum), you can use the script at cpanelproxy.net

FAQ: Can I change the ports cPanel & WHM uses?
http://unofficial-support.com/node/view/47

 

I used the web-based auto-installer to install the webmail proxy for a customer, and it worked PERFECTLY!

http://cpanelproxy.net/

- Scott

 

If you did want to install for all your customers at once, I've written a HOW-TO:

HOW-TO: cPanel Proxy 0.4.1
http://unofficial-support.com/node/view/50

 

Will this work on subdomains?

As in if I have clients using my subdomain, are they able to access it via webmail.subdomain.domain.com?

Is there a way to make it subdomain.domain.com/webmail or domain.com/webmail?

 

Frankly all I did was I installed it using MY web hosting domain, and then I let any users use it that can't do webmail the normal way.

So, if your web hosting company is www.somewebhost.com, then you install it using your somewebhost.com account, and make it webmail.somwebhost.com. Tell your users to use that if they can't get it to work the other way due to firewall/port problems.

Saves you from having to deal with installing this mod a zillion times for customers.

- Scott