Forums

Resolved
0 votes
Hello all,
I've a strange problem since yesterday. I can connect to my clearos using ssh with the root account but not in the web interface. It doesn't say the password is wrong but it's just doing ... nothing; ..
I can't restart the system because it's in use but is there a way I could reinitializee the GUI ?
Thanks :)
Wednesday, September 26 2018, 06:29 AM
Share this post:
Responses (15)
  • Accepted Answer

    nuke
    nuke
    Offline
    Saturday, May 13 2023, 12:53 PM - #Permalink
    Resolved
    0 votes
    Had a strange thing happen this morning. Despite getting to the webconfig login screen, I could not login.

    As I solved the issue I thought I'd add what I did in case someone else has the same issue.

    After ssh login I saw that the date and time was in 2017 not 2023 as expected.

    Changing the time with `date -s 'yyyy-mm-dd hh:mm:ss'` to today's date & time, allowed the webconfig to work properly again.

    For some reason the NTP server sync has failed and was off. I re-enabled the NTP server and all is OK.

    I hope this is helpful.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 26 2018, 05:42 PM - #Permalink
    Resolved
    0 votes
    A better fix now is either a:
    yum clean all && yum update

    or
    yum clean all && yum update theme-clearos-admin


    The devs have pushed a fix and it should sort itself out overnight on its own.
    The reply is currently minimized Show
  • Accepted Answer

    ZonderMet
    ZonderMet
    Offline
    Wednesday, September 26 2018, 03:47 PM - #Permalink
    Resolved
    0 votes
    #Same problem on a ClearOS Business Edition
    #When I try the solution I get a "No package available" on every package.

    Never mind. A yum update did the trick.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 26 2018, 09:34 AM - #Permalink
    Resolved
    0 votes
    ok, it worked, thanks Nick :)
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 26 2018, 09:29 AM - #Permalink
    Resolved
    0 votes
    I can get round it with a:
    yum downgrade clearos-framework-7.5.30-1.v7 app-base-2.5.25-1.v7 app-base-core-2.5.25-1.v7 app-docker-2.5.24-1.v7 app-docker-core-2.5.24-1.v7
    Leave out the docker bits if you do not have it installed. This will not work on Community.

    I am contacting the devs.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 26 2018, 09:08 AM - #Permalink
    Resolved
    0 votes
    ok, so it is an update problem..
    should I contact the support ?
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 26 2018, 08:57 AM - #Permalink
    Resolved
    0 votes
    Hmm.... I can't log into my production box .....
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 26 2018, 08:33 AM - #Permalink
    Resolved
    0 votes
    I've just updated my VM with those (and a few others) and I don't see any problem.

    You can enable and disable webconfig debugging - link. The debug log should appear as /var/log/webconfig/debug.log but note I won't be able to understand it!
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 26 2018, 08:07 AM - #Permalink
    Resolved
    0 votes
    ... seems there was ..

    Sep 26 03:15:24 Updated: clearos-framework-7.5.35-1.v7.noarch
    Sep 26 03:15:27 Updated: 1:app-base-core-2.5.32-1.v7.noarch
    Sep 26 03:15:28 Updated: 1:app-base-2.5.32-1.v7.noarch
    Sep 26 03:15:28 Updated: 1:app-marketplace-core-2.5.2-1.v7.noarch
    Sep 26 03:15:29 Updated: 1:app-marketplace-2.5.2-1.v7.noarch
    Sep 26 03:15:30 Updated: 1:app-openldap-core-2.5.3-1.v7.noarch
    Sep 26 03:15:31 Updated: kexec-tools-2.0.15-13.el7_5.1.x86_64
    Sep 26 03:15:45 Updated: 2:microcode_ctl-2.1-29.16.el7_5.x86_64
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 26 2018, 08:04 AM - #Permalink
    Resolved
    0 votes
    Please check your yum log for recent updates.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 26 2018, 08:02 AM - #Permalink
    Resolved
    0 votes
    Oooh.
    I tested the login on another system and I've the same problem ... I wonder if there was an update on the systems which causes this problem ?
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 26 2018, 07:59 AM - #Permalink
    Resolved
    0 votes
    Those errors are normal. You can get round them by using a Let's Encrypt certificate if you really want.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 26 2018, 07:33 AM - #Permalink
    Resolved
    0 votes
    Could it have anything to do with certificates ?
    I've the followin errors :


    [Wed Sep 26 09:25:30.373415 2018] [ssl:warn] [pid 9413] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)
    [Wed Sep 26 09:25:30.413644 2018] [auth_digest:notice] [pid 9413] AH01757: generating secret for digest authentication ...
    [Wed Sep 26 09:25:30.414472 2018] [lbmethod_heartbeat:notice] [pid 9413] AH02282: No slotmem from mod_heartmonitor
    [Wed Sep 26 09:25:30.416533 2018] [ssl:warn] [pid 9413] AH01906: RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
    [Wed Sep 26 09:25:30.416557 2018] [ssl:warn] [pid 9413] AH01909: RSA certificate configured for homela.poweredbyclear.com:81 does NOT include an ID which matches the server name
    [Wed Sep 26 09:25:30.416678 2018] [ssl:warn] [pid 9413] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)
    [Wed Sep 26 09:25:30.456399 2018] [mpm_prefork:notice] [pid 9413] AH00163: Apache/2.4.6 (ClearOS) OpenSSL/1.0.2k-fips configured -- resuming normal operations
    [Wed Sep 26 09:25:30.456504 2018] [core:notice] [pid 9413] AH00094: Command line: '/usr/sbin/webconfig -D FOREGROUND'



    but in another way I can connect to my server using openvpn ...
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 26 2018, 07:26 AM - #Permalink
    Resolved
    0 votes
    Hello Nick,
    Thanks for the advice :)
    Yes, LDAP is running

    [root@srv-cos ~]# service slapd status
    Redirecting to /bin/systemctl status slapd.service
    ● slapd.service - OpenLDAP Server Daemon
    Loaded: loaded (/usr/lib/systemd/system/slapd.service; enabled; vendor preset: disabled)
    Active: active (running) since dim. 2018-09-23 03:48:14 CEST; 3 days ago
    Docs: man:slapd
    man:slapd-config
    man:slapd-hdb
    man:slapd-mdb
    file:///usr/share/doc/openldap-servers/guide.html
    Main PID: 22899 (slapd)
    CGroup: /system.slice/slapd.service
    └─22899 /usr/sbin/slapd -u ldap -h ldap://127.0.0.1/


    Unfortunately, restarting the webconfig didn't solve the problem ... I'll have a look in the logs ..
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 26 2018, 07:21 AM - #Permalink
    Resolved
    0 votes
    Can you check if LDAP is running:
    service slapd status
    If it is not, try this fix.

    To restart the GUI do a:
    service webconfig restart
    The reply is currently minimized Show
Your Reply