[Bug]: Issue using AutoMaker behind ReverseProxy

[eals2019]

Operating System

Linux

Run Mode

Docker

App Version

Latest

Bug Description

I'm having a lot of issues running AutoMaker behind a reverse Proxy. As I'm reviewing the project, it looks like AutoMaker is setup with client-side processing, and it is hard-coded to use Localhost:3008 for the server access. Is this an intentional design, or am I missing something? I've tried to find videos or documentation on this, but it seems that there is none.

Steps to Reproduce

1. Run docker compose project using the docker-compose.yml (after updating based on my needs)
2. Create routes via Nginx Reverse Proxy or CloudFlare tunnel.
3. Web UI loads, but indicates that server is unavailable after 5 failed attempts. Testing on the server works fine.

Expected Behavior

I would like to have the ability to specify the server's address to be able to route traffic directly to the server, not using localhost.

Actual Behavior

3. Web UI loads, but indicates that server is unavailable after 5 failed attempts. Accessing on the server works fine.

Screenshots

No response

Relevant Logs

Additional Context

No response

Checklist

• I have searched existing issues to ensure this bug hasn't been reported already
• I have provided all required information above

[Material-Scientist]

Here's a working config: #391 (comment)

Make sure you tell the UI where to find the server and use proper cors & https headers.

I'm able to connect via traefik to the fronend and have the frontend connect to the server via envoy-proxy.