Server Technology PPNT Manuel d'utilisateur télécharger pdf (Page 48)

Chapter 4 | Testing your deployment 48

Admin Console doesn’t start after deployment on master machine

The most common solutions are:

1 On the Admin Console Start Page, click Start Admin Console.

1 Open a web browser on the master machine and enter http://localhost:16001.

Cannot start Admin Console from a remote machine

If you cannot start Admin Console from a remote machine but you can from the master machine,

the most common solutions are:

1 Ensure that you’re using the correct port in the URL:

https://[host]:16000/admin-console

Note that Admin Console always uses an HTTPS connection on port 16000 from remote

machines. You can also use http://[host]/admin-console, which works because it is

automatically redirected to HTTPS on port 16000. See

“Starting Admin Console” on page 51.

1 If the master machine has a firewall enabled, then you must open the ports required by

FileMaker

Server to communicate with users and administrators. For open ports required by a

single-machine deployment, see

“Before you begin” on page 9. Otherwise, see “Before you

begin installing on multiple machines” on page 25.

Web browsers display a certificate message

Most web browsers display a certificate error or warning message when you use an HTTPS

connection to go to any web page hosted by the FileMaker

Server web server. This includes

Admin Console, the Start Page, and any FileMaker

WebDirect or Custom Web Publishing solution

that uses an HTTPS connection. Displaying this message is expected behavior if your

FileMaker

Server deployment uses the SSL certificate provided with FileMaker Server.

The most common solutions are:

1 To proceed to the desired page, users can click the option in the web browser to continue.

1 To prevent this error message, see “Requesting an SSL certificate” on page 68.

Clients cannot see databases hosted by FileMaker Server

The firewall settings on the master machine may be blocking the display of databases to clients.

See

“Before you begin” on page 9 and “Before you begin installing on multiple machines” on

page 25 for more information on which ports need to be unblocked in firewalls.

Also, a client running FileMaker Pro 11 or earlier or FileMaker Go 11 or earlier cannot see files that

are hosted by FileMaker

Server 13. You must use FileMaker Pro 12, FileMaker Pro 13,

FileMaker

Go 12, or FileMaker Go 13 to open files that are hosted by FileMaker Server 13.

Apache web server used by FileMaker Server stops responding (OS X)

The most common solution is to ensure that no other websites or other HTTP services in OS X

are using the same ports required by the web server used by FileMaker

Server. For example, if

you have the OS

X Server application installed and use it to enable HTTP services such as

websites or the wiki, the existing Apache instance installed in OS

X may be re-enabled after

FileMaker

Server is installed. Therefore to ensure the Apache instance used by FileMaker Server

works normally, you may need to configure any other HTTP services to use different ports from

the ports that FileMaker

Server uses, disable other HTTP services, or uninstall the OS X Server

application.

1 2 ... 43 44 45 46 47 48 49 50 51 52 53 ... 82 83

Commentaires sur ces manuels

Pas de commentaire

Server Technology PPNT Manuel d'utilisateur Page 48

Commentaires sur ces manuels

Produits connexes et manuels pour Logiciel de base de données Server Technology PPNT