ispconfig structure

I will explain first how I understood the situation I am referring to and then I will post the question.

all "services" like phpmyadmin interface and webmail interface are served on http(s)://mydomain:81/phpmyadmin etc.

Now I noticed some users are accessing their resources from work and behind firewalls, so many are getting the error

Code:

Access Denied (connect_method_denied)
Your request attempted a CONNECT to a port "81" that is not permitted by default.
This is typically caused by an HTTPS URL that uses a port other then the default of 443.

so I thought to transfer those "services" to the actual apache2 installation. First I guess I would need to find the code for it in httpd.conf and transfer it to apache2.conf

How would I go ahead and change the links inside ispconfig so when they click phpmyadmin they go straight to http(s)://theirdomain.com/phpmyadmin ?

And by the way I just realized that in order to click phpmyadmin the must already have accessed port 81 any idea if I could also serve the ispconfig on a normal port 80 i.e. by http(s)://config.theirdomain.com

Any ideas ? has anyone ever thought about this? What is your opinion ? I think I should at least provide a separate acces to webmail via port 80 se ppl can at least check their mails from work

Or he could use *pound* to do a sort of virtual hosting and redirect admin.domain.tld:80 to ispconfig.domain.tld:81

Gosh, I like pound. I've got the same firewall-issue, and if you've got a lot of domains, it's not funny to have to update every instance of phpmyadmin and webmail with every release. Of course, there's also the possibility to point users to a site at port 80 where you host a phpmyadmin and webmail for all user-domains.

the ispcfg server listening cannot listen on port 80 as that would block the actual apache2 listening for all the domains... I can only get through the firewall on port 80 with http and 443 with https ... Now if pound is listening on 443 that will not allow me to have anything listening on that port as well...

seems like no solution for me but after googling for pound it sounds like a nice tool

i set up ispconfig following the manual's instructions.....when setting it up, there is a section in the general setting for server settings.....it asks for the domain name under which the ispconfig system can be reached....i've entered the domain name, but now when i entered the ip address of the server in the ip address section and save everything, it won't bring up ispconfig when i type www.candlevolt.com:81 what am i doing wrong? do i need to enter the public ip 206.xxx.xxx.xxx?

i set up ispconfig following the manual's instructions.....when setting it up, there is a section in the general setting for server settings.....it asks for the domain name under which the ispconfig system can be reached....i've entered the domain name, but now when i entered the ip address of the server in the ip address section and save everything, it won't bring up ispconfig when i type www.candlevolt.com:81 what am i doing wrong? do i need to enter the public ip 206.xxx.xxx.xxx?

Also, how the heck do I add a site that is the web site of the administrator of the entire server? Does the administrator also have to be a reseller and a client to simply add a site? If so, isn't that a bit redundant?

Also, how the heck do I add a site that is the web site of the administrator of the entire server? Does the administrator also have to be a reseller and a client to simply add a site? If so, isn't that a bit redundant?

Click to expand...

We figured this out on our own......it seems that if there is a router in the mix, you need to make sure that port 81 is opened.....also, the name servers must be set up correctly....unfortunately, nothing was mentioned in the manual about the port enabling......sorry to take up space, but hey, when there's a question, who better to go to than the ones that know the answers.