• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Filemaker and firewall - port 5003

N

nick_b

Guest
Hi,

We're having a spot of trouble - we've installed Filemaker Server (so far we've tried v5.5 and v7) on our Server2003 box (just installed last week) and are having trouble connecting to the databases remotely. It should simply be a case of specifying the IP address for the server in the FM client. FM uses port 5003 (this is IATA approved) and we suspect it's probably a firewall issue.

So far I've set rules in Plesk for TCP and UDP on port 5003, and have also edited the Plesk\admin\bin\pfwmng.js file to include this port for both TCP and UDP (as was suggested on another thread at http://forum.swsoft.com/showthread.php?threadid=17107), but still no joy. I've also added port 5003 to the c:\WINDOWS/system32\drivers\etc\services file as per a suggestion I found on a Filemaker forum.

Is there anything else in Plesk I might be missing?

Many thanks
 
Back
Top