mac can't connect to the upload feature

[Aussie John]

HI If I try to upload a database I get - "No Connection" dialog.

 

Based on another forum I checked access to port 443 and it seems to be open.

Any thoughts?

 

Possible related facts:

The Web server status is grayed out in the console.

I cannot access the console from a remote computer any more. (I thought I had fixed this previously but is back again as an issue).

Cannot access web direct. (again, thought I had fixed this previously but is back again as an issue)

 

cheers

John

 

[Wim Decorte]

Yes, those issues are related.  Fix those first, mainly the admin console and you should be able to upload too.

 

Can you still access the admin console on the server machine itself?

What kind of errors do you get when you start the web server on the FMS machine?

[Claus Lavendt]

I can't see from your post, whether the server is on windows or mac, but Wim is right. You need to get the webserver started as that is the one, handling port 443, which is used for upload.

If you are on mac, you can try this in the terminal:

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

or

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

 

If that does not work, try to restart the server machine.

[Aussie John]

 

Hi Wim and Claus

 

--Can you still access the admin console on the server machine itself?

yes

--What kind of errors do you get when you start the web server on the FMS machine?

I can't start the web server and it is grated out. There is no button to select like the other services.

(I presume FMS is creating the web server and the MacOSX web server should be off)

 

I have restated the server and run the commands as suggested (see result below)

 

/usr/sbin/httpd -k graceful -D FILEMAKER -f /Library/FileMaker Server/HTTPServer/conf/httpd.conf

httpd not running, trying to start

(48)Address already in use: make_sock: could not bind to address [::]:80

(48)Address already in use: make_sock: could not bind to address 0.0.0.0:80

no listening sockets available, shutting down

Unable to open logs

exit code 1

 

I can't find anything which has control of the port 443 or 80

[Claus Lavendt]

This seems to be Apache, that is running.

Yes, it should be, so the confusing part here is that it is loaded with Mac OS X configuration, and thereby using port 80 and 443.

You need to shut down webservice in the Mac OS X server app. It should show there, that it is running.

Alternatively you can sudo apachectl stop in Terminal

 

Then try again and maybe a machine restart after is needed.

[Aussie John]

I ended up reinstalling filemaker server which temporarily fixed all the connection issues. After a couple of weeks the web server has turned itself  off although there have been no other changes that I know of, and console web direct and file uploads have died. Although I did update java.

Probably against the rules but my Server also runs mail and filesharing.

are these likely issues?