Nate Adams

I had forgotten to port forward 2283, but I got the same thing after doing that. 502 Bad Gateway nginx error

it is my public ip, should I make it my internal ip?

The reason why I never responded was because I was setting up a domain name and https. But now I changed the VITE_SERVER_ENDPOINT to `https://immich.mydomain.com/api` and I'm getting the exact...

My domain points all requests (on all subdomains) to my public ip, my router forwards requests from 2283 to my private ip port 2283, and then nginx (nginx proxy manager)...

To follow up with this, I see the following I'm pretty sure I have the .env set up right. Unless there's some trick to getting this to work with Portainer?

I think this is a step in the right direction. Now the page loads initially and looks good and then the requests to `https://immich.mydomain.com/api/user/me` and `https://immich.mydomain.com/api/user/count` give a 502 response...

Thanks for the quick response! Ok, so I went through the process of deploying the ASI Loader and added some-game.exe as a non stream game again. Unfortunately it gives me...

The game is Sonic Heroes:  (the `modding-tool` folder is my Reloaded II directory) And here is a video of what happens when I add Tsonic_win.exe as a non-steam game...

I believe the repository code has this fixed, but the latest repo code hasn't been published to npm.

I was able to get things working with the npm code after manually doing the changes listed here: `src/index.js`: * `module.exports.parseResume` => `module.exports.parseResumeFile` *`parseIt.parseResume` => `parseIt.parseResumeFile` `src/utils/libs/processing.js`: * `mime.lookup` =>...