[BlueOnyx:23814] Re: After manual install of 5210R can't access server
f.kaegi at fairtalk.com
f.kaegi at fairtalk.com
Sun May 3 04:24:58 -05 2020
I did what you suggested and all looks good.
1) Before that, I noticed that ETH0 has no link connected, it seems the
cable is connected to ETH2.
I then configured ETH2 with onboot=yes and assigned the IP addresses to
broadcast, network, netmask, ipaddr, and dns0.
Now I can log in to the GUI and it brings me to the BlueOnyx 5210R
Here, in the system settings it shows for the Primary Interface the MAC
address of ETH0 (no IP addresses), for the Third Interface the correct IP
addresses, but no MAC Address.
When I finish the Setup-Wizzard I get the error:
An uncaught Exception was encountered
Message: Call to undefined function find_free_device()
Line Number: 516
Looking at line 516 in Wizard.php I see "$new_device =
Does it matter to which port the Ethernet cable is connected? Should I ask
the housing provider to connect the cable to ETH0?
Or how else can I solve this issue?
2) May I ask you another question?
Presently my old 5208R box is running with 5 IP addresses.
I will now use Easy Migrate to migrate all relevant content to this new
Then the housing provider will assign my "old" IP addresses to the new
How can I avoid that user content, particularly emails, that are still
coming in to the old server are not lost forever during the time the housing
provider requires to switch the IP addresses from the old to the new server?
Thank you for your kind attention and support.
All the best
From: Blueonyx <blueonyx-bounces at mail.blueonyx.it> On Behalf Of Michael
Sent: Sunday, 3 May 2020 03:29
To: blueonyx at mail.blueonyx.it
Subject: [BlueOnyx:23813] Re: After manual install of 5210R can't access
> I got a new server running CentOS 8 and manually installed 5210R
> following step-by-step the guidelines on
> At the end of the process it showed how and where to reach the GUI
> interface. However, when I enter xxx.xxx.xxx.xxx:81/login I get the
> error: This site cant be reached xxx.xxx.xxx.xxx took too long to
> I have SSH access to the server via a remote maintenance interface.
> How can I troubleshoot the problem?
Login by SSH as "admin" (password should be "blueonyx") and "su -" to become
If that doesn't work, try to login as "root" with either the password
"blueonyx" *or* whatever the password was before.
Check the running processes. See if "admserv" is running. You can also check
that with "systemctl status admserv".
Possibly there are still initial setup tasks running, which can take several
minutes. You can check that by running "tail -f /var/log/messages" and see
if there are frequent CCEd messages other than the ones from "Active
Check if firewalld is disabled:
systemctl status firewalld
If it is, you might want to stop and disable it:
systemctl stop firewalld
systemctl disable firewalld
Once all setup tasks are done and firewalld is disabled, AdmServ should be
With best regards
Blueonyx mailing list
Blueonyx at mail.blueonyx.it
More information about the Blueonyx