changing administration port

[hangab@…]

When the administration port changed and the modifications are saved, the gui shows 4 modul to restart. After the third which is the firewall it stuck. And from that point the admin is closed out, since non of the admin ports works. Not even on the localhost.

It can be solved by restarting zentyal from terminal. (etc/init.d/zentyal restart) With this the new ports will work.

[jamor@…]

Hello Hangab and thanks for reporting,

I think this is due to firewall rules. Which Internal Network and external rules have you?. Are you trying to connect through a internal or a external interface?.

Regards,

Javier

[hangab@…]

Hello Javier,

I tried everything at that time. Even on the server locally the  https://localost with both port (old and new). The only way out was restarting zentyal on the terminal.

I also tried firewall rule to accept everything on internal network. New terminal connection could have been estabilished during this problem, all the functions were working (mailserver, gateway, usercorner (so the appache had to work as well) only the administration page could not be reached.

regards,

Gabor

[jamor@…]

Hello Hangab,

I see this error occurs when the port is already in use. To which port you changed the administration port?.

You can see the active tcp ports with the command 'sudo neststat -tlnp'.

The bug here is that we need more port validation; some used ports are detected but others, like the 53 in my system, not.

Regards,

Javier

[jamor@…]

I have added code in [67fc38407fda2] to be more strict on which port numbers we accept

[hangab@…]

Hello Javier,

I wouldn't think the port I tried was in use. After a clean install just to get the port out from the "normal" portscan interval, I wanted to use port 13443.

The inner side is not really clean for me, however after stucking on the GUI, I initiated the restart of Zentyal manualy as root from terminal. This finished everything with the settings and after the desired new port was working fine. Since terminal (putty over ssh) with root permission had no problem, I had thought this to a kind of permission problem, where the gui has no right to finish restarting which was initiated through the "old" port number.

Netstat shows the 13443 port number only for apache2 now.

hangab

[jamor@…]

Thanks for the feedback Hangab. I could only reproduce this problem when the port is in use. I will let closed this ticket until we are sure that it appears with other ports.

Anyway, if someone else has this problem to fix the server which the bad port, he could restore a backup with the command '/usr/share/zentyal/restore-backup' or use this procedure:

1) Execute sudo /usr/share/zentyal/redisvi to edit the Zentyla ocnfiguration iwth the editor 'vi' . (Look in the web for instructions about using vi if you are not familiarized with it(

2) Look for this portion of text:

--- key: /ebox/modules/apache/port type: string value: '4430' ---

3) Change the value to 443 (standard https port) and exit saving changes

4) Execute 'sudo /etc/init.d/zentyal apache restart'

Regards,

Javier

[hangab@…]

Thanks Javier. I agree on keep this ticket closed, since even the problem occur, it is only occur once per server install. Also it has an easy workaround. It is no point to spend resources on track it.

hangab