Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Workspace » Port conflict with Kerio Connect (Same port 80 for both services)
  •  
Grenelle

Messages: 4
Karma: 0
Send a private message to this user
Hi,
I installed Kerio Workspace beta on the same server we dedicate to Kerio Connect, and I cannot access to Kerio Workspace admin, for default port 80 is already used by Kerio Connect.
Is it a way to associate another port to Kerio Workspace?
Friendly
Fran├žois

[Updated on: Thu, 07 October 2010 09:24]

  •  
stk_jj

Messages: 47
Karma: 0
Send a private message to this user
PortNo's are stored at /usr/local/kerio/workspace/tomcat/conf/catalina.properties
  •  
Grenelle

Messages: 4
Karma: 0
Send a private message to this user
Thanks.

Ok for modifying ports 80 (http) and 443 (https).

But for Admin port 4040?
  •  
Terry

Messages: 4
Karma: 0
Send a private message to this user
The admin for Kerio Worspace is on the same ports (80 and 443) just with a trailing /admin

So http(s)://workspace/ would become;
http(s)://workspace/admin/login/ to access the Workspace administrative interface.

Kerio connect does use 4040 for the web admin, but Workspace just has 80 and 443. (I do have a winodws install, so that may make a difference.)
  •  
Jarda Snajdr (Kerio)

Messages: 221
Karma: 12
Send a private message to this user
Hello,

the Workspace Admin console is also available at https://localhost:4060/admin - useful when the server fails to bind to the standard ports 80 and 443. This is similar to what the Kerio Connect admin is doing on port 4040.

At this moment, it is difficult to figure out what is going on when the server startup fails. We will improve the diagnostics for the final version.

Jarda
  •  
Terry

Messages: 4
Karma: 0
Send a private message to this user
The /workspace/tomcat/conf/catalina.properties file dosn't list that port. (But it *is* there Wink
  •  
stk_jj

Messages: 47
Karma: 0
Send a private message to this user
Jaroslav Snajdr wrote on Thu, 07 October 2010 14:47
the Workspace Admin console is also available at https://localhost:4060/admin - useful when the server fails to bind to the standard ports 80 and 443. This is similar to what the Kerio Connect admin is doing on port 4040.


ah - that's a nice one!
  •  
Grenelle

Messages: 4
Karma: 0
Send a private message to this user
Thanks
Admin works fine in HTTP mode (the port I defined) but not via HTTPS port (443 replacement or 4060).
  •  
Micric

Messages: 4
Karma: 0
Send a private message to this user
That is only on the Mac.

Under Linux, I am using Ubuntu, you will find it under /opt/kerio/workplace/tomcat/conf/catalina.properties
  •  
wdebitewari

Messages: 29

Karma: 0
Send a private message to this user
You can also fix this with proxypass.

Check (also) this link
  •  
Ghiyath

Messages: 21
Karma: 0
Send a private message to this user
Try to add "4060 port" manually on the kerio firewall admin console > Services > Add > TCP > equal to 4060
  •  
KerioFanBoy

Messages: 1
Karma: 0
Send a private message to this user
Hi all,

Thanks in advance for any help or suggestions you can offer.

First of all, I've spent a few hours searching both the kerio forums and wider web for a solution on this, and I apologise if one already has been posted, but I haven't been able to find it.

Secondly, I apologise for the fact that I have had to put in weirdly formatted url examples in particular the use of \\ rather than //, however I am prevented from entering correctly formatted ones as I haven't posted more than 5 posts.

This thread is a bit old, and it is possible, even probable that later versions of workspace have changed some of the information previously offered in this thread, however my problem is to a large degree an extension on this old theme, in particular.

Quote:
PortNo's are stored at /usr/local/kerio/workspace/tomcat/conf/catalina.properties


Quote:
Thanks.

Ok for modifying ports 80 (http) and 443 (https).

But for Admin port 4040?



My problem is as follows:

I need to set up multiple kerio workspace instances (using the virtual appliance version hosted on ESXi 4.1)
on a single public IP address and NAT (or more correctly PAT) the traffic through kerio control to the correct instance based on port.

I can work out a suitable solution for all of SSH, HTTP, and HTTPS access however it is a requirement that I be able to give individual instance administrators access to the admin console, and despite

Quote:
The admin for Kerio Worspace is on the same ports (80 and 443) just with a trailing /admin

So http(s):\\workspace/ would become;
http(s):\\workspace/admin/login/ to access the Workspace administrative interface.

Kerio connect does use 4040 for the web admin, but Workspace just has 80 and 443. (I do have a winodws install, so that may make a difference.)


I find that that any attempt to access https:\\url.domain.com:custom_port/admin automatically redirects to port https:\\url.domain.com:4060/admin/login (presumably it has changed from 4040 since the quoted post)

Obviously I cannot map port 4060 through to every instance of workspace.

As far as I can see, to remedy this I need to be able to be able to do either one or more of:

a./ customise the workspace admin port away from 4060.
b./ change the workspace admin redirect url so it redirects to a port other than 4060.
or
c./ set up a kerio control rule which directs traffic to a specific instance based on the inbound url, kind of like a virtual host type arrangement. ie. traffic inbound with a url of url1.domain.com forwards to a different instance/private IP than traffic inbound with a url of url2.domain.com despite the fact that they both resolve to the same public IP.

I can't seem to find a way to make any of these solutions work, any ideas, hints or pointers would be most welcome.

Cheers


Previous Topic: File History import (sharepoint)
Next Topic: Will workspace 2.0 replace Dropbox?
Goto Forum:
  


Disclaimer:
Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Current Time: Fri Oct 20 05:07:52 CEST 2017

Total time taken to generate the page: 0.00516 seconds
.:: Contact :: Home ::.
Powered by: FUDforum 3.0.4.