TrueNAS container crashing

[KevDog]

I should probably make two posts, but what the heck. Here's my issue. I'm running truecommand in a docker container via the following docker-compose file entry:

Code:

  truecommand:
    image: ixsystems/truecommand:nightly
    container_name: truecommand
    restart: unless-stopped
    networks:
      - net
    ports:
      - 81:80
      - 4343:443
    volumes:
      - /var/truecommand:/data
    environment:
      - TZ=America/Chicago

I also have a nginx reverse proxy in front of truecommand (currently only http). Here's my nginx.conf virtual domain file:

Code:

server {
    listen 80;

        server_name truecommand.<domain>.com;

        access_log /var/log/nginx/truecommand.<domain>.com.access.log main buffer=32k;
        error_log /var/log/nginx/truecommand.<domain>.error.log;

    keepalive_timeout 65;

    # Allow large attachments
    client_max_body_size 128M;

    location / {

                proxy_set_header Host $host;
                proxy_pass http://office.<domain>.com:81/;
                proxy_redirect off;
    }
}

So my problems:

Taking the reverse proxy out of the process:
1. I can access the login screen. I can authenticate. My freenas installation is shown.

I click on the freenas server, and I get this:

Unfortunately the only thing I get in the docker logs is this:
UI Socket Closing: QDateTime(2020-10-23 02:51:50.039 CDT Qt::TimeSpec(LocalTime)) "4" "127.0.0.1"

Is there a way to increase the log level on the docker image to see why this is failing??? I've used this docker image before and can only tell you I wasn't getting this problem like a week ago. Crashing only occurs with Chrome Version 86.0.4240.111 and Firefox works OK..


#2 - Introduce the reverse proxy. I attempt to authenticate and I'm left with just the background of the authentication screen. I dont get taken to the image above. Are there some headers I need for nginx to make this reverse proxy function correctly?

 

[aervin]

Hey @KevDog , we're aware of this weird Chrome issue on the nightly builds and we're working to find a fix ASAP. Sorry for the inconvenience.

 

[aervin]

@KevDog I'm finding that everything works fine in Canary, so I'm thinking this will be resolved in vanilla Chrome in a future update. Hopefully sooner than later.

 

[KevDog]

@aervin

Thanks for confirming the bug at least. Glad to know my setup isn't borked.