- Joined
- Feb 23, 2019
- Messages
- 8
- Reaction score
- 4
Hello
As I'm challenged by Linux command line, have finally figured one way to change my FQDN, have benefited from the work of others so much, here's my donation of how-to.
Probably this is already on-line, where I didn't find it? Surely there are many other ways to accomplish such.
Releasing the FQDN is well documented already.
I found my re-install "stuck" due to my inability to run find the 3CX setup on login from my remote machine. Didn't want to setup direct login to the "host" machine.
Unlike a direct host login where the 3CX setup is readly to run (see below) when login from remote machine the3CX setup on on a different terminal (tty)
Running the 3CXStartWizard.sh from tty1 failed due to same process running on tty2. (Probably there was a way to run both, which I don't know)
So as a work-around I killed the tty2 processes, then started them on tty1.
Details of how I was stuck and the solution I used: (all run as root)
1. From Linux bash terminal I'd log on to my remote Debian 3cx install. For which I'd saved a backup without license or FQDN (well documented).
a. Run the /usr/sbin/3CXCleanup wizard
b. Reboot
2. Log back in.
3. Get stuck because from my remote machine login below was on another tty. I didn't know how to switch to.
3CX
"Welcome to the 3CX Configuration Tool,
Help https//www.3cx.com,
Press ESC to go back.
Select how to run the tool:
(1) Using a Web Browser
(2) From the Command LIne
Enter option:
Good luck
Mo===
As I'm challenged by Linux command line, have finally figured one way to change my FQDN, have benefited from the work of others so much, here's my donation of how-to.
Probably this is already on-line, where I didn't find it? Surely there are many other ways to accomplish such.
Releasing the FQDN is well documented already.
I found my re-install "stuck" due to my inability to run find the 3CX setup on login from my remote machine. Didn't want to setup direct login to the "host" machine.
Unlike a direct host login where the 3CX setup is readly to run (see below) when login from remote machine the3CX setup on on a different terminal (tty)
Running the 3CXStartWizard.sh from tty1 failed due to same process running on tty2. (Probably there was a way to run both, which I don't know)
So as a work-around I killed the tty2 processes, then started them on tty1.
Details of how I was stuck and the solution I used: (all run as root)
1. From Linux bash terminal I'd log on to my remote Debian 3cx install. For which I'd saved a backup without license or FQDN (well documented).
a. Run the /usr/sbin/3CXCleanup wizard
b. Reboot
2. Log back in.
3. Get stuck because from my remote machine login below was on another tty. I didn't know how to switch to.
3CX
"Welcome to the 3CX Configuration Tool,
Help https//www.3cx.com,
Press ESC to go back.
Select how to run the tool:
(1) Using a Web Browser
(2) From the Command LIne
Enter option:
- So find above running and kill it as follows.
- run ps -ax | grep tty2
- kill the processes containing 3CX. Run ps -ax | grep tty2 again to check that 3CX processes are not running. Kill them again if missed any.
- Once those processes are dead we can run the configuration startup from the tty1 where we're logged on.
- Run /usr/bin/3CXStartWizard.sh and the above familiar configuration options appear on tty1.
Good luck
Mo===