pc No Admin Console Remotely, no https

[Pbeyrouty]

I am having trouble connecting to the admin console from another computer. I know that I need to connect with https://ipaddress:16000, but I'm not having any success. When on the server computer I can connect using localhost:16001. The problem seems to be that https isn't starting.

 

I am running the server that is included as part of a TechNet membership on a Windows 8 64 bit computer with 4 gb of RAM.  I didn't have a web server setup on the machine originally but the install seems to have started it. When I checked the settings in IIS manager the FM Web Site didn't have https activated. I changed the advanced settings but it still doesn't start https after a reboot. I think it is also preventing me from uploading a database from FileMaker Pro.

 

I have attached a screenshot of IIS Manager with the settings. Has anyone had a similar problem or know what I might do to correct this problem? Any help would be appreciated.

[Wim Decorte]

When on the server computer I can connect using localhost:16001. The problem seems to be that https isn't starting.

 

 

This is FMS13, right?  Your profile says 11.

 

If you can connect on port 16001 from the machine itself that means that https is working.  You seem to think that it is not: what kind of errors do you get?

[Pbeyrouty]

Sorry it is FMS 13. I can connect using 16001 on the machine itself. however I don't think that requires https. I tried connecting using https://localhost:16001 it says there is an SSL error. When I just do localhost:16001 it works fine. When connecting remotely using https://localhost:16000 it get's timed out.

[bledrew1]

I'm having a similar problem. Our IT folks uninstalled FMSA12 on my test server (Windows Server R2 Enterprise, SP1. The server is running with the sample file just fine. I thought I'd try uploading a test DB using the FMA13 client, but it didn't accept our normal credentials. I'm betting the whole thing failed before he set the admin user and password. He had installed it, removed it and installed it again with the same results.

 

I'd be interested to see what anyone else has discovered. I have my test OS X install at home that went without a hitch.

 

Bill

 

Bill LeDrew

Wizards of the Coast| ORC: FMP Support | The Creative Group

[Wim Decorte]

Our IT folks uninstalled FMSA12  I thought I'd try uploading a test DB using the FMA13 client, 

 

that doesn't work AFAIK, FM13 clients can only upload to FMS13.  To upload to FMS12 you can do that straight from the admin console

[bledrew1]

Pardon any confusion. I meant to say after they installed FMSA13, I attempted to upload a test database that we use. After further investigation and visits to IT, I discovered that the install fails at the end when it tries to open the Admin Console so that the username and password can be entered. The browser opens "localhost:16001/admin-console" and comes up with Unable to connect. I didn't know yesterday that this is where it failed. It left the sample database being served, but no ability to open the Admin Console or upload our test database from FMA13 (no credentials got entered).

 

What could be preventing it from connecting? FMSA12 had been running for a year as a test server without incident. I had them let me uninstall and do the install myself with precisely the same result.

[Steven H. Blackwell]

 

he browser opens "localhost:16001/admin-console" and comes up with Unable to connect.

 

Please try Port 16000, not 16001.

 

Steven

[bledrew1]

I did that after the install tried Port 16001 and failed.

 

"localhost:16001/admin-console" generating by the installer produces "Unable to connect" error message

"localhost:16000/admin-console" says "Connecting" and then dies with a blank page

 

I'm going to have them put up another VM instance and try it again. Will report my results.

[dave17]

I am experiencing a similar situation. I installed FM13 Server on a VM. 

 

 Web Publishing Engine shows that it isn't running. When I click the "switch" to start it, within about 5 seconds it turns itself off....

 

Trying to figure out how to post a screen shot here. standby.

 

Still puzzled as to why my screen looks so much different than it does on the vtc site training videos for FMS 12. Is there a big difference btwn FMS12 and FMS13 in the Admin Console?

[Wim Decorte]

There's HUGE difference between FMS12 and 13 when it comes to the admin console. totally different animal.

 

The FMS and OS log files will tell you why the FMS web publishing engine refuses to start.

[dave17]

Still not really getting it. I'm not sure what I need to do?

[dave17]

I am attempting to run this on a virtual machine Windows Server, which has IE8 installed. Some of the IE security settings are greyed out. "Custom Level" under the IE Internet Options Security Tab is greyed out on each of the 4 choices.

[Wim Decorte]

Supported version of Windows?  Correct version of java?

 

The windows application event log and windows system event log will have more detail than the FMS log.  There's no simple answer to these things usually, just a lot of elimination and sleuthing.

[jordanmohr77]

My web publishing is working fine but when I try to connect to the admin console remotely via port 16000, I get the same failure to connect. I get this with Mac and Windows servers.

[Agnes Riley]

I'm having the same problem: cannot connect to the admin console on port 16000. Port 16001 works locally. This was working fine until last time I rebooted.

 

I can't even telnet on the port on the machine itself:

 

east02:~ administrator$ telnet 127.0.0.1 16000

Trying 127.0.0.1...

telnet: connect to address 127.0.0.1: Connection refused

telnet: Unable to connect to remote host

 

Any ideas here?

 

it's a Mac OSX server 10.8.5.

 

Thanks,
Agi

[Rick Whitelaw]

I have the opposite problem. Can connect remotely without a problem but can't connect locally. Don't much care as the server box is just that. A box.

[Agnes Riley]

I have the opposite problem. Can connect remotely without a problem but can't connect locally. Don't much care as the server box is just that. A box.

That's even more strange. What port did you try? 

[Rick Whitelaw]

Not at a computer at the moment. Port is correct. This happened after the latest FMS update.

[Agnes Riley]

Addition: fmp link stopped working, as well. And all this worked just fine for almost a year.

 

Does anyone have an idea?

[Claus Lavendt]

Agnes, a few things to try;

1) Is the apache server running ?

 

In Terminal, run this_

sudo /Library/Filemaker Server/HTTPServer/bin/httpdctl start

 

This command will ask the apache to start and use the FMS settings.

 

sudo launchctl start com.filemaker.fms

 

This command will tell the launch service of the OS to always start apache with the FMS settings.

 

2) Is admin server running ?

 

If that is running, you need to check if the admin server is running. This is a java based process, which you can start from the Terminal with:

fmsadmin start ADMINSERVER

 

If this does not work, you can try repair disk permissions.

If this does not help, try a machine restart

Still problems, I am affraid that reinstall will be the fastest solution....

[IdealData]

Have has been the culprit in many cases like this.

FWIW don't take OS X 10.9 past the original release. It will fail to start FMS after a reboot, but can be manually started. Sorry, details not to hand.

Sorry, Java is usually the culprit.

[Claus Lavendt]

I can say that we have several FMS13 running on 10.9 and they run perfectly.

However, you need to pay attention to the fact that OSX server wants to be in charge of the Apache web server. So is FMS.

When you update and/or enable any service in OSX server, that uses Apache, it will write into launch services, that the configuration it should use, has to be the OSX server apache configurations. Then the CWP, WebDirect and admin console of FMS will not work. That is why you need to turn over the control of apache to FMS as a start.

sudo launchctl start com.filemaker.fms 

 

will do that. Then make sure that all parts of FMS is running, which can be done from the Terminal. Please refer to FileMakers documentation.

 

Regarding java, that is actually several things, which many confuse...

Java Webstart is an application environment, which the previous admin console was written in. This has been a pain for the last 3-4 years, as it has been updated extremely many times, due to security issues. Add to that, it has been pretty buggy, so it was great to learn that the admin console of FMS13 was rewritten in html5.

Java is actually a pretty rock solid technology, which is mainly used as server environments and run a lot of server applications, including some of the components in FMS.

JavaScript also shares the name "java", though it really has nothing to do with Java or JavaWebstart.

[haseebiqbal]

The tech told me to uninstall Antivirus and turn off firewall then reinstall n configure FM Server, which I am going to do now....

Will update you, how I go...

[haseebiqbal]

Yes it worked. Just uninstalled AV...

[Grouchy]

On 25 September 2014 at 1:37 AM, Claus Lavendt said:

Agnes, a few things to try;

1) Is the apache server running ?

 

In Terminal, run this_

sudo /Library/Filemaker Server/HTTPServer/bin/httpdctl start

Thanks Claus! 

This actually helped me with this problem. I also could not access remotely via https://Host:16000/admin-console

It turns out when I start the web server, there's a syntax error, so I commented out line 78 from https-ssl.conf and the https started ok.

I am just not commenting this has any adverse effect, but since SSLCompression is Off anyways?

[removed] >>>> httpdctl start
========== start ==========
Wed Apr 6 09:52:39 SGT 2016
/usr/sbin/httpd -k start -D FILEMAKER -f /Library/FileMaker Server/HTTPServer/conf/httpd.conf
AH00526: Syntax error on line 78 of /Library/FileMaker Server/HTTPServer/conf/extra/httpd-ssl.conf:
Setting Compression mode unsupported; not implemented by the SSL library
exit code 1