Had a license problem and fixed it

Discussion in 'LiquidFiles General' started by Paul Nickerson, Dec 6, 2018.

  1. Paul Nickerson

    Paul Nickerson New Member

    Dec 6, 2018
    Likes Received:
    I recently rebooted our LiquidFiles instance in AWS, and it came back up with the message "license server timeout, or license code not found on license server" on the license page. I noticed that another person on this forum had a license issue in AWS recently, so I wanted to share the fix here in case it helps anyone else.

    During startup, systemd-hostnamed changed the host name of the system (seen in /var/log/messages). Maybe this was caused by AWS's cloud-init script; I'm not sure. But the fix was to go to System > Hostname and fix it there. Everything started working immediately for me after that.

Share This Page