Jump to content

Gog

Members
  • Content Count

    279
  • Joined

  • Last visited

Community Reputation

11 Good

About Gog

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Montreal

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Gog

    [Support] Linuxserver.io - Grocy

    I did an update of the container yesterday and the grocy template is not there. The samples timestamps look like they are from the last container restart but no groxy. How can I force that?
  2. Gog

    [Support] Linuxserver.io - Grocy

    Care to share the LE config?
  3. Gog

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    In nginx config, change proxy pass to the url you use internally to reach HA Sent from my SM-G930W8 using Tapatalk
  4. Gog

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    I just tried installing the container and it is configured as host network. It may not like the bridge config. Can you try changing network type to host in the container config? Nging won't reach it after that but we can fix it later Sent from my SM-G930W8 using Tapatalk
  5. Gog

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    I forget the choices for connection type.. Is there TCP and rdp? Does the container start with that port? Something else may be using it. I dont see it in your screenshot though so it's probably not that... Sent from my SM-G930W8 using Tapatalk
  6. Gog

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    That looks good. Sent from my SM-G930W8 using Tapatalk
  7. Gog

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    It looks like you are not exposing any ports to the outside. It works for nginx because the traffic goes through proxynet, the custom network interface. In HomeAutomation, add a port mapping with the + at the bottom of the container settings. Map 8123 to 8123. You are telling the docker to let requests that hit your unraid server on port 8123 to let that through the HomeAutomation container on port 8123.
  8. Gog

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    Hi Speedmax For local access you are not going through nginx. When you use 192.168.*.* the settings you need to look at are your docker container port mapping. Can you share the docker config? Sent from my SM-G930W8 using Tapatalk
  9. Gog

    6.6.6 system crash

    I made a backup of the flash before rebuilding it and the files are clean, I dont think it was ransomware
  10. Gog

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    Are you using a custom network interface? This: set $upstream_bitwarden Bitwarden Will not work until you do. With a custom docker network interface, internal DNS will translate "Bitwarden" to 10.10.8.28 but it won't work with the standard bridge interface. Sent from my SM-G930W8 using Tapatalk
  11. Gog

    6.6.6 system crash

    OK so at least now I'm up, I rebuit the USB with Unraid.USB.Creator.Win32-1.5b and used a different USB port.
  12. Gog

    6.6.6 system crash

    Good morning My unraid server is unstable. I get system crashes every 7-14 days. Last time I gathered logs with the troubleshooting tools and I got this: Feb 3 02:46:51 Tower kernel: mdcmd (1097): spindown 9 Feb 3 02:46:55 Tower kernel: BUG: unable to handle kernel paging request at fffff8ffdfd3f008 Feb 3 02:46:55 Tower kernel: PGD 0 P4D 0 Feb 3 02:46:55 Tower kernel: Oops: 0000 [#2] SMP PTI Feb 3 02:46:55 Tower kernel: CPU: 3 PID: 9875 Comm: php-fpm Tainted: G B D W 4.18.20-unRAID #1 Feb 3 02:46:55 Tower kernel: Hardware name: Supermicro X10SL7-F/X10SL7-F, BIOS 3.0 04/24/2015 Feb 3 02:46:55 Tower kernel: RIP: 0010:unmap_page_range+0x69b/0x88a Feb 3 02:46:55 Tower kernel: Code: 0c ff 8c 24 88 00 00 00 e9 89 00 00 00 48 b9 ff ff ff ff ff ff ff 01 b8 f5 ff 7f 00 48 21 f9 48 c1 e0 29 48 c1 e1 06 48 01 c1 <4c> 8b 41 08 48 89 c8 41 f6 c0 01 74 04 49 8d 40 ff 4c 8b 40 08 41 Feb 3 02:46:55 Tower kernel: RSP: 0018:ffffc90003cfbce8 EFLAGS: 00010286 Feb 3 02:46:55 Tower kernel: RAX: ffffea0000000000 RBX: 000015271688c000 RCX: fffff8ffdfd3f000 Feb 3 02:46:55 Tower kernel: RDX: ffff880101607e98 RSI: 0000000000000000 RDI: 3e00003bff7f4fc0 Feb 3 02:46:55 Tower kernel: RBP: 00001527169cf000 R08: 0000000000000000 R09: ffffea00103316c0 Feb 3 02:46:55 Tower kernel: R10: ffffea00103316c0 R11: 0000000000000001 R12: ffff8802b8d414e0 Feb 3 02:46:55 Tower kernel: R13: 0000000000000000 R14: ffffc90003cfbde8 R15: ffff880283d2f268 Feb 3 02:46:55 Tower kernel: FS: 0000000000000000(0000) GS:ffff88041fcc0000(0000) knlGS:0000000000000000 Feb 3 02:46:55 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 3 02:46:55 Tower kernel: CR2: fffff8ffdfd3f008 CR3: 0000000001e0a005 CR4: 00000000001606e0 Feb 3 02:46:55 Tower kernel: Call Trace: Feb 3 02:46:55 Tower kernel: unmap_vmas+0x4b/0x7f Feb 3 02:46:55 Tower kernel: exit_mmap+0xc8/0x16a Feb 3 02:46:55 Tower kernel: ? __switch_to_asm+0x35/0x70 Feb 3 02:46:55 Tower kernel: mmput+0x4d/0xe5 Feb 3 02:46:55 Tower kernel: do_exit+0x3b0/0x8b0 Feb 3 02:46:55 Tower kernel: ? handle_mm_fault+0x159/0x1a8 Feb 3 02:46:55 Tower kernel: do_group_exit+0x9a/0x9a Feb 3 02:46:55 Tower kernel: __x64_sys_exit_group+0xf/0xf Feb 3 02:46:55 Tower kernel: do_syscall_64+0x57/0xe6 Feb 3 02:46:55 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Feb 3 02:46:55 Tower kernel: RIP: 0033:0x152714ce7a66 Feb 3 02:46:55 Tower kernel: Code: Bad RIP value. Feb 3 02:46:55 Tower kernel: RSP: 002b:00007ffe8d00e668 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 Feb 3 02:46:55 Tower kernel: RAX: ffffffffffffffda RBX: 0000152714de5760 RCX: 0000152714ce7a66 Feb 3 02:46:55 Tower kernel: RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000 Feb 3 02:46:55 Tower kernel: RBP: 0000000000000000 R08: 00000000000000e7 R09: ffffffffffffff78 Feb 3 02:46:55 Tower kernel: R10: 0000000000000006 R11: 0000000000000246 R12: 0000152714de5760 Feb 3 02:46:55 Tower kernel: R13: 0000000000000007 R14: 0000152714dee428 R15: 0000000000000000 Feb 3 02:46:55 Tower kernel: Modules linked in: ipt_REJECT iptable_mangle tun macvlan veth xt_nat ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat reiserfs xfs md_mod ipmi_devintf igb i2c_algo_bit x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc ipmi_ssif aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_uncore intel_rapl_perf mpt3sas ahci sata_mv libahci i2c_i801 button i2c_core video thermal fan backlight pcc_cpufreq raid_class scsi_transport_sas ipmi_si ie31200_edac [last unloaded: i2c_algo_bit] Feb 3 02:46:55 Tower kernel: CR2: fffff8ffdfd3f008 Feb 3 02:46:55 Tower kernel: ---[ end trace 70b9f100a2be40b9 ]--- Feb 3 02:46:55 Tower kernel: RIP: 0033:0x150b13e38207 Feb 3 02:46:55 Tower kernel: Code: Bad RIP value. Feb 3 02:46:55 Tower kernel: RSP: 002b:00007ffe46f9e000 EFLAGS: 00010206 Feb 3 02:46:55 Tower kernel: RAX: 0000150b1547a097 RBX: 0000150b1547a2c4 RCX: 0000150b1547a097 Feb 3 02:46:55 Tower kernel: RDX: 0000000000000008 RSI: 0000150b1547a129 RDI: 0000000000000000 Feb 3 02:46:55 Tower kernel: RBP: 00007ffe46f9e0d0 R08: 0000000040000000 R09: 000055ac2a6af2e0 Feb 3 02:46:55 Tower kernel: R10: 0000000000000000 R11: 0000150b1540fe30 R12: 000055ac2a77b420 Feb 3 02:46:55 Tower kernel: R13: 00000000000f4241 R14: 0000150b13e85000 R15: 0000150b13e8cff0 Feb 3 02:46:55 Tower kernel: FS: 0000000000000000(0000) GS:ffff88041fcc0000(0000) knlGS:0000000000000000 Feb 3 02:46:55 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 3 02:46:55 Tower kernel: CR2: 0000150b13e381dd CR3: 0000000001e0a005 CR4: 00000000001606e0 Feb 3 02:46:55 Tower kernel: Fixing recursive fault but reboot is needed! Google searches did not help much. After this, the server won't boot up, it's falling in EFI shell. I had this before but with the original USB stick (512MB, it's been a while) troubleshooting tools didn't have enough room to save logs. Now the kingston DTSE9 16GB won't boot. Troubleshooting logs are attached. Any help is appreciated. tower-diagnostics-20190203-0229.zip FCPsyslog_tail.zip
  13. Gog

    [Support] Linuxserver.io - Nextcloud

    That is exactly what @mkono87 did just before you. Use LetsEncrypt handle the SSL certificate for you and reverse proxy nextcloud through it. No need to go through the certificate generation and worry about renewal, letsencrypt is free and auto renews.
  14. Gog

    [Support] Linuxserver.io - Nextcloud

    I wouldn't be too worried about the hash size. Do you get the same behavior if you try to connect with https://192.168.0.50:446 ? Do you see the connection go through in the letsencrypt access log?
  15. Gog

    [Support] Linuxserver.io - Nextcloud

    config.php looks good. I'm not sure 'trusted_proxies' => ['letsencrypt'] is essential, it was missing from mine for the site-config, change proxy_pass https://$upstream_nextcloud:443; to proxy_pass https://192.168.0.50:446; and you can remove: set $upstream_nextcloud nextcloud; That's the bit that needs the custom network interface.