Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

FileMaker Pro is not connecting to FileMaker Server through NGINX reverse proxy but works throughout /fmi/webd/

Featured Replies

  • Newbies

Hi,

I'm new in FileMaker, so forgive me if that is something simple to solve.

My servers:

  1. FileMaker Server
  2. Ubuntu Ubuntu 22.04.2 LTS
  3. FileMaker Server 20.1.1.38
  4. Acme.sh Wildcard SSL
  5. IP: 10.10.10.10 (as an example)
  6.  
  7. NGINX Reverse Proxy
  8. Ubuntu Ubuntu 22.04.2 LTS
  9. nginx/1.18.0
  10. Acme.sh Wildcard SSL
  11. IP: 10.10.10.20 (as an example)
  12.  
  13. Windows Pro 22H2
  14. FileMaker Pro 20.1.1.35

Everything works perfectly when connected either by:

https://filemaker.domain/fmi/webd/

or

https://reverseproxy.domain/fmi/webd/

 

FileMaker Pro connects ok when using https://filemaker.domain but does not when using https://reverseproxy.domain

 

Error: Connection Failed.

 

The NGINX "currently" is running on the LAN. The config it is using is the one created by "/opt/FileMaker/FileMaker\ Server/Tools/NginxLB/nginxLB.sh", with the change of:

from:

  1. upstream backend {
  2. #using ip hash with nginx open source
  3. #hash $binary_remote_addr consistent;
  4. #using sticky session with nginx plus
  5. sticky cookie srv_id expires=1h path=/;
  6. #server 10.10.10.10:443;
  7. }

 

to:

  1. upstream backend {
  2. hash $binary_remote_addr consistent;
  3. server 10.10.10.10:443;
  4. }

Running from the Windows Client:

telnet reverseproxy.domain 5003

Connecting To filemaker.pbti.org...Could not open connection to the host, on port 5003: Connect failed

 

telnet filemaker.domain 5003

Works

 

Trying to solve this, I have added in NGINX, this code below, without any result:

  1. server {
  2. listen 5003;
  3. listen 16000;
  4. listen 16002;
  5. server_name reverseproxy.domain;
  6. return 301 https://filemaker.domain$request_uri;
  7. }

On the reverproxy:

  1. tcp 0 0 0.0.0.0:16002 0.0.0.0:* LISTEN 1720/nginx: master
  2. tcp 0 0 0.0.0.0:16000 0.0.0.0:* LISTEN 1720/nginx: master
  3. tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 1720/nginx: master
  4. tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1720/nginx: master
  5. tcp 0 0 0.0.0.0:5003 0.0.0.0:* LISTEN 1720/nginx: master

 

 What I'm missing?

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.