bhcompy

does that persist past reboot?

Thank you for the help. It ended up being that the swag template for kimai is not suitable for this scenario. I found this on the kimai website for reverse proxies, plus I set environmental variables on the kimai container for TRUSTED_PROXIES and TRUSTED_HOSTS based off some old github comments from the owner (similar to the instructions in the Nextcloud swag conf) server { listen 443 ssl; listen [::]:443 ssl; server_name kimai.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth (requires ldap-location.conf in the location block) #include /config/nginx/ldap-server.conf; # enable for Authelia (requires authelia-location.conf in the location block) #include /config/nginx/authelia-server.conf; # enable for Authentik (requires authentik-location.conf in the location block) #include /config/nginx/authentik-server.conf; location / { proxy_pass https://internalIPaddressForKimaiContainerGoesHere:443/; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-Host $host:$server_port; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Port $server_port; } # Redirect HTTP to HTTPS, in case an invalid (plain HTTP) request was sent to port 443 error_page 497 https://$host:$server_port$request_uri; }

I'm looking for some guidance here, as I'm not sure what I'm doing wrong. I setup Kimai to work through SWAG on a non-standard HTTPS port and SWAG keeps dropping the port. SWAG is setup on its own network with Kimai and properly resolves. The external HTTPS port for SWAG is 8450. When I hit https://kimai.mydomain.com:8450, it spins for a bit and then redirects to https://kimai.mydomain.com/en/login, which doesn't work. If I manually modify the URL to https://kimai.mydomain.com:8450/en/login, then it works, but the very next thing I do within the webpage repeats the problem. Obviously it's not really usable in that state. Nextcloud container is setup basically in the same way, and works without issue. I've been searching around the documentation, the nginx documentation (which is really sparse and esoteric), stackoverflow, reddit, here, etc and trying all manner of things and I just can't figure out what changes I need to make to kimai.subdomain.conf to get it to work consistently. absolute_redirect off or on don't seem to change anything, port_on_redirect on or off don't seem to do anything, some people suggest adding a / to the end of the proxy_pass URL and that just breaks the website (502), some suggest using proxy_redirect but I can't seem to get that to work no matter what I try, so any help would be appreciated. I've added the conf file below. Some of the commented out items are things that I tried and couldn't get to work based on documentation from kimai, the swag default, the configuration for nextcloud I have that works in the way I'm expecting this to work, etc. Also, if I understand what I've read right, I think the second location here is if using kimai as a subfolder rather than a subdomain? ## Version 2024/07/16 # make sure that your kimai container is named kimai # make sure that your dns has a cname set for kimai server { listen 443 ssl; listen [::]:443 ssl; server_name kimai.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth (requires ldap-location.conf in the location block) #include /config/nginx/ldap-server.conf; # enable for Authelia (requires authelia-location.conf in the location block) #include /config/nginx/authelia-server.conf; # enable for Authentik (requires authentik-location.conf in the location block) #include /config/nginx/authentik-server.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable for ldap auth (requires ldap-server.conf in the server block) #include /config/nginx/ldap-location.conf; # enable for Authelia (requires authelia-server.conf in the server block) #include /config/nginx/authelia-location.conf; # enable for Authentik (requires authentik-server.conf in the server block) #include /config/nginx/authentik-location.conf; include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app kimai; set $upstream_port 443; set $upstream_proto https; #set $dest_port 8450; proxy_pass $upstream_proto://$upstream_app:$upstream_port; #proxy_pass https://172.18.0.4/; #proxy_redirect $upstream_proto://$upstream_app:$upstream_port/ $upstream_proto://$upstream_app:$dest_port/; #absolute_redirect off; #port_in_redirect on; #proxy_set_header Host $http_host; #proxy_set_header X-Real-IP $remote_addr; #proxy_set_header X-Forwarded-Host $host:$upstream_port; #proxy_set_header X-Forwarded-Server $host; #proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; #proxy_set_header X-Forwarded-Proto $scheme; #proxy_set_header X-Forwarded-Port $upstream_port; proxy_buffering off; } location ~ (/kimai)?/api { include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app kimai; set $upstream_port 443; set $upstream_proto https; #set $dest_port 8450; proxy_pass $upstream_proto://$upstream_app:$upstream_port; #proxy_pass https://172.18.0.4/; #proxy_redirect $upstream_proto://$upstream_app:$upstream_port/ $upstream_proto://$upstream_app:$dest_port/; #absolute_redirect off; #port_in_redirect on; #proxy_set_header Host $http_host; #proxy_set_header X-Real-IP $remote_addr; #proxy_set_header X-Forwarded-Host $host:$upstream_port; #proxy_set_header X-Forwarded-Server $host; #proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; #proxy_set_header X-Forwarded-Proto $scheme; #proxy_set_header X-Forwarded-Port $upstream_port; proxy_buffering off; } }

When I setup my server everyone said grab an old USB2 flash drive and use that because USB3 was not preferred and there's a lot of poor quality/counterfeit newer ones out there, so that's what I grabbed. Thank you for your help edit: Removing the unRAIDServer folder did the trick

It's 2gb. I haven't written anything to it. Never touch it. Just tried to upgrade to 6.12.13 and it failed due to space limitation. Drive is 90% utilized. I will delete unraidserver and see what happens. If not, I will delete the previous directory as there is no need to revert version at this point as it's been stable for months on .10. Thank you

Any idea what can be deleted from the flash drive? Mine has ballooned and now I cannot upgrade as there is not enough space. The "previous" directory looks like an obvious candidate as the bzfirmware file is huge, but I can't find anything here indicating if this can actually be deleted. There's also the unraidserver directory, which appears to be old upgrade files? Could those safely be deleted?

Anyone know if the QXP-800eS-A1164 (Asmedia 1164) PCIe SATA controller will work with autotune? Secondarily, if I run the autotune command, it doesn't persist on reboot, correct? So I could try it and if I have a problem, I could reboot and it would resolve?

Getting a weird error trying to start up Observium. I haven't run it for a while and had uninstalled it temporarily, so I'm not sure if there's something new I'm supposed to do? I don't see anything that sticks out, though. Trying to log in: DB not connected, please check database connection configuration. DB Error 2002: No such file or directory From the logs: 230111 10:08:01 mysqld_safe Starting mariadbd daemon with databases from /config/databases Jan 11 10:08:01 e66c9d301cea syslog-ng[14]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0' Jan 11 10:08:01 e66c9d301cea syslog-ng[14]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0' Jan 11 10:08:01 e66c9d301cea syslog-ng[14]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0' Jan 11 10:08:01 e66c9d301cea syslog-ng[14]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0' Database exists. Fixing file permissions. Jan 11 10:08:01 e66c9d301cea syslog-ng[14]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0' just keeps logging that perpetually. It looks like it's finding the db, so it's not a path issue(and it's the default, verified it's still there). Not sure where to go from here. Any help would be appreciated

That helps keep the login/stop the refreshing, but now the status on the dropdown says "My Servers error. graphql is offline"

What is the implication of doing this(particularly if you're using modprobe i915 for Plex)? Blacklist is always a fun term

Did you end up going with any particular enclosure? Recommendations for eSATA enclosures seem to be slim, at least ones that aren't 5+ years old