bigbangus

I just have to highlight that mapping /cache in the container to /tmp/espcache on the host results in significantly faster compiling speeds in ESPHome. So if you feel like it takes forever to update your ESPHome devices because of slow compiling, I will definitely recommend this change.

Yup it's dialed now. Thank you sir. is this worthy of a template update? I feel like this should be standard. And on a personal note, welcome to the bald head club. It suits you well!

Why does ESPHome utilize all the processors available to my docker service when building the firmware to update an ESPHome device?

Fixed in the post. Sorry for the typo fellas if it wasn't hard enough already to chase the occ debacle. Glad I could help.

Spoke too soon. It's now apparently: sudo -u abc php /app/www/public/occ db:add-missing-indices

Any idea why this command in the nextcloud console window doesn't work anymore? I'm trying to run sudo -u abc php /config/www/nextcloud/occ db:add-missing-indices but it's like the file is not there anymore

You add them to the nextcloud proxy-conf in swag. Here is what mine looks like with all the comments removed: server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name nextcloud.*; add_header Strict-Transport-Security "max-age=15768000; includeSubdomains; preload;"; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app nextcloud; set $upstream_port 443; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_buffering off; proxy_max_temp_file_size 2048m; } } and then make sure your proxy.conf which is referenced above is back to default in swag as such: ## Version 2023/02/09 - Changelog: https://github.com/linuxserver/docker-swag/commits/master/root/defaults/nginx/proxy.conf.sample # Timeout if the real server is dead proxy_next_upstream error timeout invalid_header http_500 http_502 http_503; # Proxy Connection Settings proxy_buffers 32 4k; proxy_connect_timeout 240; proxy_headers_hash_bucket_size 128; proxy_headers_hash_max_size 1024; proxy_http_version 1.1; proxy_read_timeout 240; proxy_redirect http:// $scheme://; proxy_send_timeout 240; # Proxy Cache and Cookie Settings proxy_cache_bypass $cookie_session; #proxy_cookie_path / "/; Secure"; # enable at your own risk, may break certain apps proxy_no_cache $cookie_session; # Proxy Header Settings proxy_set_header Connection $connection_upgrade; proxy_set_header Early-Data $ssl_early_data; proxy_set_header Host $host; proxy_set_header Proxy ""; proxy_set_header Upgrade $http_upgrade; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Method $request_method; proxy_set_header X-Forwarded-Port $server_port; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Ssl on; proxy_set_header X-Forwarded-Uri $request_uri; proxy_set_header X-Original-Method $request_method; proxy_set_header X-Original-URL $scheme://$http_host$request_uri; proxy_set_header X-Real-IP $remote_addr;

what do you mean exactly still suffering the same issue while still being able to hit it fine from your public domain url? also what have you configured in the Nextcloud ONLYOFFICE settings for urls?

So I managed to solve the issue. I believe I had a combination of errors in my swag nginx config files. I returned all my swag nginx configs back to default (ssl.conf, proxy.conf, resolver.conf, nginx.conf). Also here is my onlyoffice proxy-conf GNU nano 7.2 onlyoffice.subdomain.conf ## Version 2023/05/31 # make sure that your onlyoffice documentserver container is named documentserver # make sure that your dns has a cname set for documentserver server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name onlyoffice.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app OnlyOfficeDocumentServer; set $upstream_port 443; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; #proxy_redirect off; } } And finally, delete all your browser cache and restart your browser. Also after trying to open a document in nextcloud, if you still get a refuse to connect, do a Ctrl+Shift+R and it may work. This was my major problem. I had solved the issue but kept going back because my browser cache was all jacked up. Hope it works, let me know.

I don't know if this is the right place to do this, but want to say a general thank you to all the contributors and lime tech developers for Unraid 6.12. The GUI enhancements are excellent and the new appdata backup plugin is really polished. I've not dabbled in ZFS yet, but just really happy with Unraid. I started my journey into the home lab around COVID time and Unraid is what sparked my curiosity for self-hosted applications. It's now one my main hobbies and passions and I don't think I would have explored as far as I did without Unraid and all the wonderful SpaceInvaderOne video tutorials. Thank you.

Ok got it. That's a day I'll never get back but at least I'm back on the latest branch of minio/minio First you have to make the bucket on the new S3 instance then you have to copy over the bucket contents. mc mb minio/bucket mc cp --recursive minio_old/bucket/ minio/bucket/

PAIN! I got this far. What are the commands to copy buckets from 'minio_old' to 'minio'?

what about this part? Jun 10 04:16:25 unraid CA Backup/Restore: done! Jun 10 04:16:27 unraid kernel: NVRM: GPU at PCI:0000:04:00: GPU-43924f5b-3d1d-9fb3-4784-c566475994c7 Jun 10 04:16:27 unraid kernel: NVRM: Xid (PCI:0000:04:00): 79, pid='<unknown>', name=<unknown>, GPU has fallen off the bus. Jun 10 04:16:27 unraid kernel: NVRM: GPU 0000:04:00.0: GPU has fallen off the bus. Jun 10 04:16:27 unraid kernel: clocksource: timekeeping watchdog on CPU0: hpet wd-wd read-back delay of 201711390ns Jun 10 04:16:27 unraid kernel: NVRM: A GPU crash dump has been created. If possible, please run Jun 10 04:16:27 unraid kernel: NVRM: nvidia-bug-report.sh as root to collect this data before Jun 10 04:16:27 unraid kernel: NVRM: the NVIDIA kernel module is unloaded. Jun 10 04:16:27 unraid kernel: clocksource: wd-tsc-wd read-back delay of 201779346ns, clock-skew test skipped! Jun 10 04:16:27 unraid kernel: xhci_hcd 0000:04:00.2: Unable to change power state from D3hot to D0, device inaccessible And then this at the very end before the involuntary reboot: Jun 10 04:17:18 unraid kernel: clocksource: timekeeping watchdog on CPU15: hpet read-back delay of 201719282ns, attempt 3, marking unstable Jun 10 04:17:18 unraid kernel: tsc: Marking TSC unstable due to clocksource watchdog Jun 10 04:17:18 unraid kernel: TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Jun 10 04:17:18 unraid kernel: sched_clock: Marking unstable (3266968550854251, -36363093365)<-(3266932404371485, -216638034)

I had a crash this morning roughly at 4:30am. My daily backup is at 4:00am so not sure if it's related. The server has rebooted and is now operating. Could someone take a look at the logs? I send them to my pfsense syslog-ng no it should have captured the before and after. Thanks! default.log

Crickets. Can anyone help with this issue. I tried reaching to OO for support and they said Unraid not supported which I think means they just don't understand Unraid is linux + dockers. https://forum.onlyoffice.com/t/nextcloud-server-settings-pass-but-cant-open-document/4961/7 Maybe someone could share a working nginx proxy-conf with me. Here is what I have server { listen 443 ssl; listen [::]:443 ssl; server_name onlyoffice.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app OnlyOfficeDocumentServer; set $upstream_port 443; set $upstream_proto https; proxy_max_temp_file_size 2048m; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } } Healthcheck in nextcloud is true, but then opening any document I get "onlyoffice.xxx.xx refuses to connect"