Sign inSign up

safesoftware/fmeflow-nginx-proxy

By safesoftware

•Updated about 20 hours ago

NGINX proxy for serving SSL with FME Flow

Image
0

10K+

safesoftware/fmeflow-nginx-proxy repository overview

ā āš ļø Security Deprecation Notice

⁠Summary

Several image tags across these repositories have been deprecated due to a critical Remote Code Execution (RCE) security vulnerability. We strongly urge all users to upgrade to the latest patched version for their major release immediately.

For full details, please refer to our Knowledge Base Article: šŸ”— Security Update: FME Flow Remote Code Execution Vulnerability⁠

⁠Deprecated Tags

The following versions are affected and should no longer be used:

Major VersionDeprecated TagsMinimum Safe Version
2023.22023.2 – 2023.2.62023.2.6.1
2024.02024.0 – 2024.0.52024.0.5.1
2024.12024.1 – 2024.1.42024.1.4.1
2024.22025.2 - 2025.2.52024.2.5.1
2025.02025.0 – 2025.0.32025.0.3.1
2025.12025.1 – 2025.1.3.32025.1.3.4
2025.22025.2 – 2025.2.32025.2.4

⁠Action Required

Please update your deployments to use the minimum safe version (or later) for your major release as listed above. Running a deprecated image exposes your FME Flow environment to a critical security risk.

If you are unsure which version to use, we recommend upgrading to the latest available image tag.

For questions or assistance, please visit Safe Software Support.⁠


⁠FME Flow Nginx Proxy

FME Flow works hand-in-hand with FME Form. Design the workflow you want to automate in FME Form's drag-and-drop interface and then publish it to FME Flow at the push of a button.

Using FME Flow you can schedule the workspace you created to automatically run at any time interval, turn it into a self-serve process for others to run whenever they want, or have your workspace always running in real-time.

Find out more at https://fme.safe.com/platform/⁠

⁠How to use this image

This repository is part of a multi-container deployment of FME Flow. See the FME Flow documentation⁠ for detailed instructions on deploying these containers using docker-compose.

Since FME Flow is a multi-container deployment, the standard way of running these containers together is to use docker-compose with a docker-compose.yml file.

You can download the docker-compose file for the version of FME Flow you would like to deploy from our Downloads page⁠.

The environment variable EXTERNALHOSTNAME should be set to the external IP address or hostname you will use to connect to this host.

For a multi-host deployment of these containers, we recommend deploying with Kubernetes. To get started, see Deploying FME Flow with Kubernetes⁠.

We recommend running this on a machine that has at least 8 GB or RAM available. If you are using Docker for Mac or Docker for Windows you can change this in your Docker Settings.

Tag summary

Content type

Image

Digest

sha256:77830bade…

Size

116.6 MB

Last updated

about 20 hours ago

docker pull safesoftware/fmeflow-nginx-proxy:2026.4-beta