127.0.0.1 is, of course, localhost
Have you tried the machines IP:16000 ?
Also... In the console... Have you allowed for remote admin?
11th Hour Group Pty Ltd
+61 2 6687 5367
Sent from my iPad Mini
Hope you are well.
This worked fine until the last reboot. Usually I access the admin console by going to: "https://domain.com:16000/admin-console/"
There are no restrictions in admin console. Is there a switch "allow for remote admin" somewhere that I don't know of?
Whether I connect by IP or domain name, I get
This webpage is not available
I checked and my domain still works at the proper IP. The server host says there are no firewall restrictions.
I know you can connect locally via 16001, but have you tried restarting the web server? Perhaps it did not come back up properly when you rebooted.
From the terminal:
sudo apachectl graceful
...usually does the trick for me.
Yes... Pretty good thanks. I've had an Italian exchange student for two weeks and been very busy.
I think the problems might be related to the fact you have OSXServer. I could not make 13 work on 10.9 with OSXServer.... it installs it's own Apache and refuses to cooperate with the OSXServer install of Apache. I installed and uninstalled for days trying to get them to work together. It sorta worked intermittently. As soon as I deleted OSXServer the whole thing worked like a dream. I'm not sure if this is the same as 10.8 but the behaviour is the same. When FMI suggest a 2-machine deployment they really meant it this time.
I am successfully running server 13 with its own Apache on 10.9 and have configured virtual hosting for about 10 domains and Postfix for sending mail.... but I have had to split up some functions which I still need OSXServer for like wikis and mail accounts etc.
If it IS possible... I'd love to know too... Good luck!
Sent from my iPad
11th Hour Group Pty Ltd
I have the two-server install. That's what I started out with when I started offering hosting. And it's 10.8, because 10.9 had network issues. We actually had a 10.9 server that was wiped and downgraded to 10.8 per the suggestion of the hosting company.
So, let me try and reboot the second server and see if that fixes the issue.
To Be Continued...
Ok, reboot didn't help. That server is 10.8.6 by the way.
Clearly, I cannot forget anything because I haven't changed anything.
But here's the larger problem, now the fmp link doesn't work either and that's a huge issue, because that's how new users get to the database first time.
Just my 2 cents thrown out. I've been updating older FMS systems to FMS 13 (and updating versions of 13) a lot lately.
I suggest you use this URL to connect. I don't try to outsmart FMS by adding 16000 or 16001 or HTTPS. They are not needed if the install worked correctly.
The FMS 13 install places a redirect for this URL on its web server. This URL should always work to get to the FMS console. Of course you probably need to add this URL to the Java list of allowed URLs. This is very important on recent versions of Java so don't overlook it. BTW, this is may be required on each computer used to access the admin-console(s).
If it still doesn't work then I suggest you reinstall FMS. Probably something prevented a complete/correct install and/or writing of the redirect. Protect your databases by using the CLI to close all files and stop the server.
1. Turn ON indexing, this should be on so the installer can properly locate all the folders it needs for the instal process. If its a Mac use Spotlight at least once to make sure its done indexing.
2. Turn off Virus protection, you don't need it on a FMS computer. If the IS department requires it then turn it off during install and exclude the FMS folders (same as indexing) when its turned back on.
3. Restart, FMS should be set to NOT auto launch. If any launch then I suggest you 1) use the command line to stop FMS, 2) (force) quit the FMS apps before installing. Hopefully since there are no clients the DB will only have been opened and not in use.
4. Do un-install using the FMS 13 install program. I've successfully un-install FMS 11, 12, and 13.
5. Restart, this makes sure all FMS programs are not running.
6. Install FMS 13, latest version of course. §^=)
7. At end of install perform configuration.
8. I suggest also setting up Progressive Backup and disabling auto-launch on computer startup.
Everything should now be set up and working.
9. Disable (Spotlight) indexing and Virus protection scanning of the FMS folder and any live FMP data folders you may have set up outside of the FMS folders.
Hey Chocolate Man, long time no hear!
Thank you for you cents, they are always welcome.
I think something is wrong with my server, because I cannot upload files either.
I have not upgraded Java on that machine and I definitely didn’t change anything. It has been functioning for probably a year.
I’ve also never used virus protection (or any other software for that matter) on my FMS for at least a decade. FYI it’s my hosting server. So, know what I’m doing tonight: reinstalling.
Do I have to reinstall the web server machine, as well (web direct server) or just the master?
Ok, reinstalled both servers and I can confirm that I can access the admin console remotely.
Celebrate! Take the next two (2) days off.
You’re a funny guy.