my free license is expiring in a few days and i can’t access my web admin interface to update it. Neither from remote nor from localhost. Although a few months back it worked flawlessly. I always get a blank page of death on http://188.214.105.101:9000/ Anything else that i can try? The web mail client works ok. I don’t have any problems with it. On https i get a This site can’t provide a secure connection.
I’ve tried restarting the services a few times and the server also but no luck.
Anything else i can try?
Have you confirmed that you have access to that port / the port is listening? It might be that it’s not enabled. I did look up a way to turn enable it if it’s off.
Thank you for the reply. I doubt it’s the port since it used to work but no it doesn’t. Even more it doesn’t work from localhost. I’ve checked now and it has 3 rules enabled in the firewall… Checked also and Port 9000 is open on 188.214.105.101.
Till you will find the problem with the WebAdmin interface please do not forget that you could simply replace the existing axigen_lk.bin file (from the Aixgen working directory) with the one corresponding to the new license (pay attention to the keep the file read and write rights and ownership details).
After replacing that file (my recommendation is to back-up your old file) you need to restart Axigen service so it will use the new license.
I know, i kept this one as a last resort since i didn’t want to meddle with the files and might break something by replacing something else. But thank your suggestions none the less and also for the detail about ownership. I would have totally overlook that.
Now that you have a safety net for applying the license let’s check why you do not have acces to the WebAdmin interface.
Could you please:
1/ connect into CLI (like telnet 127.0.0.1 7000 from your server console)
2/ login with your admin user
3/ navigate to server context (like config server)
4/ share the output from:
show attr services
5/ navigate to webadmin context (like config webadmin)
6/ share with us the output from:
list listeners
list urlRedirects
From one of our test systems we have something like this:
support@test-9SD3:~$ telnet 127.0.0.1 7000
Welcome to AXIGEN's Command Line Interface
You must login first. For a list of available commands, type HELP
<login> user admin
<password> xxx-xxx-xxx
<#> config server
<server#> show attr services
services = (log processing smtpIncoming smtpOutgoing pop3 imap webmail cli webadmin reporting ftpBackup rpop)
<server#> config webadmin
<server-webadmin#> LIST Listeners
The list of Listeners for this service:
address | enable
-------------------------
0.0.0.0:9000 | yes
127.0.0.1:9191 | yes
:::9000 | yes
+OK: command successful
<server-webadmin#> list UrlRedirects
The list of UrlRedirects rules for this service:
address | host | port | auto
------------------------------------------
127.0.0.1:8000 | localhost | 8443 | yes
+OK: command successful
Basically we like to know if:
i/ if the webadmin service is started
ii/ if there is at least one enabled listener
iii/ if there is no urlRedirects that may prevent connecting to the WebAdmin
Thank you for the indepth walktrough services = (log processing smtpIncoming smtpOutgoing pop3 imap webmail cli webad min reporting ftpBackup rpop webmailProxy)
The list of Listeners for this service:
address | enable
-----------------------
0.0.0.0:9000 | yes
The list of UrlRedirects rules for this service:
address | host | port | auto
------------------------------------------
127.0.0.1:8000 | localhost | 8443 | yes
ok - so, as you see, the output was provided by the Microsoft-HTTPAPI server and not Axigen.
Now, if you are sure that the telnet commands were executed on the console from the Windows server where Axigen is running, I could not provide any explanation why you have another server (which is identifying as Microsoft-HTTPAPI) intercepting / responding on the same port as Axigen WebAdmin is supposed to respond so you definitely have to extend the investigations.
From Axigen side we could add another HTTP listener for WebAdmin service so you could try to connect on that port (for example, via CLI, like: config server > config webadmin > add listener 0.0.0.0:9999 > commit > save config).
ah, only now I have seen that on post #12 instead of connecting on port 9000 I’ve give you instructions to connect on port 80.
so, could you please:
1/ open a new cmd terminal on the Windows instance that is running Axigen server
2/ execute the following commands:
$ telnet 127.0.0.1 9000<press-ENTER>
GET / HTTP/1.0<press-ENTER>
<press-ENTER>
And coming back to your last question - could you please re-run the CLI commands mentioned in post #6 so we’ll see if the listener on port 9999 has been added and it is enabled?
If yes, what you get (from a web browser and telnet) when connection to it locally?
ok - so the Axigen-WebAdmin is providing an answer when connecting to 127.0.0.1 on port 9000. Nevertheless the strange part is that you get a 400 Bad Request error code but at least we are receiving something.
now, please investigate furthermore why the local opened browser get an empty page when connecting to http://127.0.0.1:9000 as I’ve no other ideas other than the obvious ones like restarting the server or checking if the webadmin folder from Axigen working directory is still on disk / have any access permissions problems / etc.
as you know, the problems like it was working before but not now do not appear from “thin air” but as a consequence of some manual / automated actions. thus my advice for you is to review what was changed / installed / updated on the Windows server between the moment “it was working before” and the moment “but not now”.
I’m glad that you’ve managed to find the main problem and fix it in the end.
Coming back on your question, I could only recommend to contact our support channel (if entitled) as “the devil is in details” especially when discussing about Windows and installation options an admin has.
