Running but unable to load properly

[bkwar201]

I am almost certain that there is a step i am missing that i just have no idea on. But following the steps i am getting the following error when i try to go to http jet-ui.domain.com:5173 . https fails entirely.
This was done on a new debian 13 lxc(proxmox) with Docker, Curl & Portainer being the only things installed before pulling the git files, editing the env's as instructed and running the deploy.sh which does start the docker.

root@docker:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
785e54bd9b03 jetkvm-cloud-selfhosted-api "docker-entrypoint.s…" 26 hours ago Up 26 hours 3000/tcp, 0.0.0.0:5172->5172/tcp, [::]:5172->5172/tcp jetkvm-cloud-selfhosted-api-1
b0b910b34b33 jetkvm-cloud-selfhosted-ui "npx serve -s /usr/s…" 26 hours ago Up 26 hours 0.0.0.0:5173->5173/tcp, [::]:5173->5173/tcp jetkvm-cloud-selfhosted-ui-1
aa1e1407a1da postgres "docker-entrypoint.s…" 28 hours ago Up 28 hours (healthy) 0.0.0.0:5432->5432/tcp, [::]:5432->5432/tcp jetkvm-cloud-selfhosted-api-db-1
a54f9f23ceac portainer/portainer-ce:lts "/portainer" 46 hours ago Up 28 hours 0.0.0.0:8000->8000/tcp, [::]:8000->8000/tcp, 0.0.0.0:9443->9443/tcp, [::]:9443->9443/tcp, 9000/tcp portainer

[bkwar201]

So i assume it is related to http vs https, not sure how to fix that exactly though.
In trying to mess with Nginx Proxy Manager i was able to get the page to load, and change it to https? But i am not able to adopt anything to either http or https i just get a 403 forbidden (i have no idea if this is something with the API or the UI side of things though)

SSL is set to use my wildcard domain, Force SSL = enabled & HTTP/2 Support = enabled

Hoping for some insight as to what was done to get this working >_<

[bkwar201]

Okay some additional info.. i was able to get this working. There were some changes that needed to be done to do so in the env's though.
First NPM (Nginx Proxy Manager)
1 - dont use wildcard certs, need to have a unique cert for each (ui & api links) otherwise access from outside breaks
2 - API proxy host -- odic has issues so add this to advanced/settings(gear), also these are the toggles
Cache Assets = disabled | Block Common Exploits = disabled | Websockets Support = enabled | Force SSL = enabled | http/2 support = disabled

proxy_buffer_size 16k;
proxy_buffers 8 16k;
proxy_busy_buffers_size 24k;
large_client_header_buffers 4 16k;

3 - UI proxy host -- add below to the advanced/settings(gear) tweak it for your ui domain, also the toggles Cache Assets = disabled | Block Common Exploits = disabled | Websockets Support = enabled | Force SSL = enabled | http/2 support = disabled

# Disable NPM default security headers that break JetKVM
more_clear_headers Content-Security-Policy;
more_clear_headers Cross-Origin-Opener-Policy;
more_clear_headers Cross-Origin-Resource-Policy;

# Allow API access
add_header Access-Control-Allow-Origin "https://jet-ui.domain.com" always;
add_header Access-Control-Allow-Credentials "true" always;
add_header Access-Control-Allow-Methods "GET, POST, OPTIONS" always;
add_header Access-Control-Allow-Headers "Content-Type, Authorization" always;

# Handle preflight
if ($request_method = OPTIONS) {
    return 204;
}

Then for the env i changed these.
4 - env-ui edits -- *unclear if these are actually needed for the env-ui
added

VITE_CLOUD_URL=https://jet-ui.domain.com

5 - env-api edits
edited

REAL_IP_HEADER=X-Forwarded-For
#this was X-Real-IP before .. this kinda makes sense that i needed to change this since i am using NPM via another machine

added at the bottom

#added via Copilot suggestion/tshooting
CLOUD_URL=https://jet-ui.domain.com