Flycast - Private server 502 Bad Gateway

I have deployed two apps one Flycast - Private Fly Proxy services


  1. Created a private IPv6 for the app
  2. Removed force_https = true from the [http_service] in fly.toml
  3. Deployed the app

In the nginx.conf of reverse proxy, I did the following

server {
  listen 80;

  # Redirect HTTP to HTTPS
  return 301 https://$host$request_uri;
server {
...other code
  location / {
    proxy_connect_timeout 90s;
    proxy_pass http://my-fly-api.flycast:3000/;
    proxy_set_header X-Forwarded-Host $http_host;
...other code

With this setup back to 502 Bad Gateway. What am I doing wrong?

I have also seen this - NGINX Reverse Proxy Flycast 502 Error, but did not work for me.

I got this to work. I had to update the flycast app .toml to the following

  internal_port = 3000
  auto_start_machines = true
  auto_stop_machines = true
  min_machines_running = 0
  processes = ["app"]

  internal_port = 3000
  protocol = "tcp"

    port = 3000
  	handlers = ["http"]

Thanks to Private networking on IPv6 - #3 by gajuro

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.