New install of remotely via Docker is no-go

[huntson]

Describe the bug
After running the docker I am unable to connect after the container is running

To Reproduce
Steps to reproduce the behavior:

1. Use the following docker compose code deployed via Portainer
   name: remotely services: remotely: container_name: remotely ports: - 5999:5000 volumes: - /volume1/docker/remotely:/app/AppData environment: - Remotely_ApplicationOptions__DbProvider=SQLite - ASPNETCORE_ENVIRONMENT=Production restart: always image: immybot/remotely:latest
2. Once the container shows healthy, attempt to access via :5999. Does not load at all
3. Click on '....'
4. Scroll down to '....'
5. See error

Remotely Version
Server (can be found on about page): Presumed latest however cannot find as not running
Agent (can be found in device card):Presumed latest however cannot find as not running

Expected Behavior
A clear and concise description of what you expected to happen.

I'd expect to be able to get to the login/register page

Additional Context
I have tried this on both a QNAP NAS and a Synology NAS (with changes in the folder path) with no luck at all.

Logs generated are as such:
[00:57:56 WRN] Storing keys in a directory '/root/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed. For more information go to https://aka.ms/aspnet/dataprotectionwarning {EventId={Id=60, Name="UsingEphemeralFileSystemLocationInContainer"}, SourceContext="Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository", ThreadId=1} [00:57:57 WRN] No XML encryptor configured. Key {334eaa2d-ab1a-478c-b589-aae9960884d1} may be persisted to storage in unencrypted form. {EventId={Id=35, Name="NoXMLEncryptorConfiguredKeyMayBePersistedToStorageInUnencryptedForm"}, SourceContext="Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager", ThreadId=1} [00:57:57 INF] Now listening on: http://[::]:8080 {EventId={Id=14, Name="ListeningOnAddress"}, SourceContext="Microsoft.Hosting.Lifetime", ThreadId=1} [00:57:57 INF] Application started. Press Ctrl+C to shut down. {SourceContext="Microsoft.Hosting.Lifetime", ThreadId=1} [00:57:57 INF] Hosting environment: Production {SourceContext="Microsoft.Hosting.Lifetime", ThreadId=1} [00:57:57 INF] Content root path: /app {SourceContext="Microsoft.Hosting.Lifetime", ThreadId=1} [00:58:18 WRN] Failed to determine the https port for redirect. {EventId={Id=3, Name="FailedToDeterminePort"}, SourceContext="Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware", RequestId="0HN5RVGNPVOP7:00000001", RequestPath="/api/healthcheck", ConnectionId="0HN5RVGNPVOP7", ThreadId=12}

[bitbound]

This isn't an issue with the Docker image or the app, but with the hosting environment. Moving this to discussions.

[bitbound]

Logs indicate the container and app started successfully. However, you're missing environment variables, which is why the app is listening on port 8080 instead of 5000. There's also no connection string for the DB.

I'm not able to provide support, and I'm not sure if you'll even be able to get it running on a NAS. I'd recommend Ubuntu + Caddy + docker-compose.