Author Topic: Unable to connect to https://localhost in Zentyal 5.0 (development edition)  (Read 13592 times)

lufegero

  • Zen Apprentice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Hi,

I have installed zentyal 5.0 and after restarting the server I cannot access the zentyal control panel. The message that appears in Firefox is "Unable to connect". I have tested with https://localhost, https://127.0.0.1 and the IP address I assigned to eth0 but the same error appears. The server pings localhost and other computers on the network and has normal browsing.

When running "nmap localhost" only port 80 appears open. It seems as if the zentyal admin page was not loaded on the web server (nginx) because when I try to access http:// localhost the welcome page of nginx loads normally.

I appreciate all the help you can give me about it.

julio

  • Guest

lufegero

  • Zen Apprentice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
I tried port 8443 but I did not get access. I scanned the server's ports with nmap and this is the output:

Starting Nmap 7.01 ( https://nmap.org ) at 2017-06-03 08:58 COT
Nmap scan report for localhost (127.0.0.1)
Host is up (0.0000090s latency).
Other addresses for localhost (not scanned): ::1
Not shown: 998 closed ports
PORT   STATE SERVICE
22/tcp open  ssh
80/tcp open  http

Nmap done: 1 IP address (1 host up) scanned in 1.67 seconds


I get the same output with the address assigned to eht0. This is strange because during zentyal installation no error was reported. It is assumed that after the restart I should be able to enter the administration page to configure zentyal.

I have even reviewed /var/log/nginx/error.log and /var/log/nginx/access.log but there is no information there yet.

Since nmap says port 443 is not open, I suppose there could be a problem with the page on the web server. I have been reviewing and in /var/www/html/ and /etc/nginx/sites-available/ I only see nginx default files. Could it be that the zentyal site has not been installed?
« Last Edit: June 03, 2017, 04:37:36 pm by lufegero »

half_life

  • Bug Hunter
  • Zen Hero
  • *****
  • Posts: 867
  • Karma: +59/-0
    • View Profile
Please run
Code: [Select]
ss -ltn
It will show what is actually [l]istening on [t]cp ports by [n]umber

This will show you if there is an issue with firewall rules.

half_life

  • Bug Hunter
  • Zen Hero
  • *****
  • Posts: 867
  • Karma: +59/-0
    • View Profile
On further thought perhaps this would be slightly better
Code: [Select]
ss -ltnp |less -p nginx
Which does everything from above plus shows the program name and PID info of the services listening to the ports. Further it loads that info into less and searches for the first occurrence of nginx. Note apache is listening to port 443 not nginx.

lufegero

  • Zen Apprentice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
I ran the commands that you indicated but the output still shows me that the server listens only for ports 22 and 80. I don't see that apache is running and I don't find it in /etc. Iptables also does not appear to be installed.

As it is a clean installation I reinstalled zentyal again but nothing changes. What can be happening in the installation? Could it be that there is some step that the installer is skipping? I don't know if zentyal will keep a log of installation.

half_life

  • Bug Hunter
  • Zen Hero
  • *****
  • Posts: 867
  • Karma: +59/-0
    • View Profile
Is the webmin service running?
Code: [Select]
sudo systemctl status zentyal.webadmin-nginx.service

megafitz

  • Zen Apprentice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Same problem here!

Is the webmin service running?
Code: [Select]
sudo systemctl status zentyal.webadmin-nginx.service

Loaded: loaded (/lib/systemd/system/zentyal.webadmin-nginx.service; static; v
Active: inactive (dead)

And I tried to start/restart, nothing happens.

half_life

  • Bug Hunter
  • Zen Hero
  • *****
  • Posts: 867
  • Karma: +59/-0
    • View Profile
Try to start the service via
Code: [Select]
sudo systemctl start zentyal.webadmin-nginx.service
and immediately thereafter check the journal to find out what the cause of the failure was.
Code: [Select]
sudo journalctl -xe

megafitz

  • Zen Apprentice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Only have this message now.

Waiting until Zentyal is ready...

half_life

  • Bug Hunter
  • Zen Hero
  • *****
  • Posts: 867
  • Karma: +59/-0
    • View Profile
I have never seen that in the journal.  Do you mean that is what is in the web browser?

megafitz

  • Zen Apprentice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
I have never seen that in the journal.  Do you mean that is what is in the web browser?
Yes, in browser.
I 'll print journal for you as soon as possible.

Code: [Select]
Jun 07 08:02:48 samba[1246]:   ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error code 110

Jun 07 08:02:54 samba[1245]: [2017/06/07 08:02:54.070622,  0] ../lib/util/util_runcmd.c:316(samba_runcmd_io_handler)
Jun 07 08:02:54 samba[1245]:   /usr/sbin/samba_kcc: ldb_wrap open of secrets.ldb

Journal red messages.
« Last Edit: June 07, 2017, 01:49:22 pm by megafitz »

megafitz

  • Zen Apprentice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
I have never seen that in the journal.  Do you mean that is what is in the web browser?
Yes, in browser.
I 'll print journal for you as soon as possible.

Code: [Select]
Jun 07 08:02:48 samba[1246]:   ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error code 110

Jun 07 08:02:54 samba[1245]: [2017/06/07 08:02:54.070622,  0] ../lib/util/util_runcmd.c:316(samba_runcmd_io_handler)
Jun 07 08:02:54 samba[1245]:   /usr/sbin/samba_kcc: ldb_wrap open of secrets.ldb

Journal red messages.

Any help?

half_life

  • Bug Hunter
  • Zen Hero
  • *****
  • Posts: 867
  • Karma: +59/-0
    • View Profile
Sorry,

I had surgery the next day and haven't been moving too quick since then.   The entry in the journal would not be unusual for a samba system that hasn't been configured yet.  I am sure there was more in the journal than you quoted.  Would you mind doing the restart and then looking at the journal immediately afterwards.  Open your focus to include more than the last few lines.

cserem

  • Zen Apprentice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Hi

I recently upgraded from 4.3 to 5.0. After this, I think I am having the same issue. Also regarding the DNS module, Im having the same symptoms described here: https://tracker.zentyal.org/issues/1984 Not sure if I had the error before, but I am assuming now it prevents systemd from starting zentyal on boot.

What seems to make it work now, is having:
Code: [Select]
service zentyal stop
sleep 5
service zentyal start
on the bottom of /etc/rc.local before exit 0
« Last Edit: June 12, 2017, 08:15:13 pm by cserem »