ich777

Yes... Jokes aside, on what system do you run the container (CPU/Motherboard/RAM)? Can you provide a screenshot from your Docker template? Are you sure the share where the game is located on stays actually on there and is not moved to the Array or whatever disk you are using? How much resources is the container using, it should look something like that (I've got a 12core CPU Intel i5-10600, the server should hover around 3 and 8 percent usage when empty and fully startet with about 14-15GB of RAM usage): (this is a completely fresh installed instance and yes, it only says Starting Server nothing more since the log gets nowadays written to a file)

What do you mean with things? If you want to edit your server I would recommend that you look at some guides like here. You only need to edit the GAME_PARAMS

My bad, try this: #!/bin/bash sleep 60 docker exec -i <CONTAINERNAME> /bin/bash -c "/usr/bin/luckybackup -c --no-questions --skip-critical /root/.luckyBackup/profiles/default.profile > /root/.luckyBackup/logs/default-LastCronLog.log 2>&1"

Thank you for the report, sadly enough the routine to install PA changed completely and I have to say since I don't play the game anymore I will deprecated the container.

Sorry, I thought that would be obvious... Maybe add a bit of sleep at the beginning, 60 seconds or so that your server can fully start up and after that start the sync: #!/bin/bash sleep 60 docker exec -i <CONTAINERNAME> /usr/bin/luckybackup -c --no-questions --skip-critical /root/.luckyBackup/profiles/default.profile > /root/.luckyBackup/logs/default-LastCronLog.log 2>&1 (I think that should work)

Exactly. Reboot will never work because it‘s a Docker container. You can create a cron schedule in Unraid that runs on reboot with something like that: #!/bin/bash docker exec -i <CONTAINERNAME> /usr/bin/luckybackup -c --no-questions --skip-critical /root/.luckyBackup/profiles/default.profile > /root/.luckyBackup/logs/default-LastCronLog.log 2>&1 This then should run the command from your cron schedule that you‘ve posted above in the container, you also have to replace <CONTAINERNAME> with you containername <- please note that I have not tested that because I‘m currently on my mobile phone.

I already posted something like that (I think it was a reddit post) but that is more like a workaround not a fix. I would recommend to investigate further why it is not working with the network check enabled.

I just tried it with the Big Jump Map 2023 and it is working just fine over here. Maybe your port forwarding is not correct?

Maybe, that's a thing you should definitely try. Maybe but what is the benefit, for your friends it would be way easier to join like it's intended. BTW I'm maybe wrong but if you give your friends access to your Tailscale network, they are basically part of your LAN and in my opinion that would be pretty bad (what if a computer on that network is infected with Malware or something like that... just saying...).

Please stop the container, delete the file "BeamMP-Server" from the main directory from the container, after that start the container and it should pull the file. If you've restarted the container multiple times please wait for at least 30 minutes before starting the container because it could be the case that you've already reached the limit from the free GitHub API calls (which the container is using).

I don't see why your card should not work: 04:00.0 Ethernet controller [0200]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] Subsystem: Mellanox Technologies ConnectX-3 10 GbE Single Port SFP+ Adapter [15b3:0055] Kernel driver in use: mlx4_core Kernel modules: mlx4_core 06:00.0 Ethernet controller [0200]: Mellanox Technologies MT27710 Family [ConnectX-4 Lx] [15b3:1015] Subsystem: Mellanox Technologies Stand-up ConnectX-4 Lx EN, 25GbE dual-port SFP28, PCIe3.0 x8, MCX4121A-ACAT [15b3:0003] Kernel driver in use: mlx5_core Kernel modules: mlx5_core 06:00.1 Ethernet controller [0200]: Mellanox Technologies MT27710 Family [ConnectX-4 Lx] [15b3:1015] Subsystem: Mellanox Technologies Stand-up ConnectX-4 Lx EN, 25GbE dual-port SFP28, PCIe3.0 x8, MCX4121A-ACAT [15b3:0003] Kernel driver in use: mlx5_core Kernel modules: mlx5_core Both your ConnectX3 and ConnectX4 are detected and running. You can delete network.cfg and network-rules.cfg from /boot/config, reboot and see if that changes anything (keep in mind that your server may have another IP and it is not reachable on the IP where it was before).

Sorry but I can‘t reproduce this error. Do you have any adblocking somewhere in your network or Unifi network gear?

Can you post a screenshot from your Docker template please? Are you sure that the container can access all data from the mapped directory? This is definitely not related to the error from the pinned post. So I assume it is now working correct?

Connect X4 cards are known to work well with Unraid. Without Diagnostics I can‘t say anything.

Did you provide steam credentials in your template? If yes, this is most likely why it‘s not working.

Try to connect a display and see if that changes anything.

You have a call trace in your syslog which is most likely the cause of the issue: Dec 16 11:57:06 Wizard-Server kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access Dec 16 11:57:06 Wizard-Server kernel: BUG: kernel NULL pointer dereference, address: 0000000000000020 Dec 16 11:57:06 Wizard-Server kernel: #PF: supervisor read access in kernel mode Dec 16 11:57:06 Wizard-Server kernel: #PF: error_code(0x0000) - not-present page Dec 16 11:57:06 Wizard-Server kernel: PGD 105f4f067 P4D 105f4f067 PUD 108c01067 PMD 0 Dec 16 11:57:06 Wizard-Server kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI Dec 16 11:57:06 Wizard-Server kernel: CPU: 0 PID: 1148 Comm: udevd Tainted: P O 6.1.64-Unraid #1 Dec 16 11:57:06 Wizard-Server kernel: Hardware name: Default string Default string/MS-WS W680 D4, BIOS H4.2G 11/26/2022 Dec 16 11:57:06 Wizard-Server kernel: RIP: 0010:klist_put+0x16/0x74 Dec 16 11:57:06 Wizard-Server kernel: Code: 03 00 31 c0 48 89 03 5b 89 e8 5d 41 5c 41 5d c3 cc cc cc cc 41 55 41 54 41 89 f4 55 53 48 8b 2f 48 89 fb 48 83 e5 fe 48 89 ef <4c> 8b 6d 20 e8 d2 9b 03 00 45 84 e4 74 10 48 8b 03 a8 01 74 02 0f Dec 16 11:57:06 Wizard-Server kernel: RSP: 0018:ffffc9000103bab8 EFLAGS: 00010246 Dec 16 11:57:06 Wizard-Server kernel: RAX: ffff888135074b80 RBX: ffff888135074ba8 RCX: ffff888135074b80 Dec 16 11:57:06 Wizard-Server kernel: RDX: ffff888103c4b410 RSI: 0000000000000001 RDI: 0000000000000000 Dec 16 11:57:06 Wizard-Server kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffff829513f0 Dec 16 11:57:06 Wizard-Server kernel: R10: 00003fffffffffff R11: fefefefefefefeff R12: 0000000000000001 Dec 16 11:57:06 Wizard-Server kernel: R13: ffff8881010cc000 R14: ffff888105d19b50 R15: ffff8881010cc0d0 Dec 16 11:57:06 Wizard-Server kernel: FS: 000014e9445d8240(0000) GS:ffff88903f400000(0000) knlGS:0000000000000000 Dec 16 11:57:06 Wizard-Server kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 16 11:57:06 Wizard-Server kernel: CR2: 0000000000000020 CR3: 000000010368e000 CR4: 0000000000750ef0 Dec 16 11:57:06 Wizard-Server kernel: PKRU: 55555554 Dec 16 11:57:06 Wizard-Server kernel: Call Trace: Dec 16 11:57:06 Wizard-Server kernel: <TASK> Dec 16 11:57:06 Wizard-Server kernel: ? __die_body+0x1a/0x5c Dec 16 11:57:06 Wizard-Server kernel: ? page_fault_oops+0x329/0x376 Dec 16 11:57:06 Wizard-Server kernel: ? do_user_addr_fault+0x12e/0x48d Dec 16 11:57:06 Wizard-Server kernel: ? exc_page_fault+0xfb/0x11d Dec 16 11:57:06 Wizard-Server kernel: ? asm_exc_page_fault+0x22/0x30 Dec 16 11:57:06 Wizard-Server kernel: ? klist_put+0x16/0x74 Dec 16 11:57:06 Wizard-Server kernel: device_del+0xb6/0x31d Dec 16 11:57:06 Wizard-Server kernel: ? i915_ggtt_probe_hw+0x593/0x5be [i915] Dec 16 11:57:06 Wizard-Server kernel: platform_device_del+0x21/0x70 Dec 16 11:57:06 Wizard-Server kernel: platform_device_unregister+0xf/0x19 Dec 16 11:57:06 Wizard-Server kernel: sysfb_disable+0x2b/0x54 Dec 16 11:57:06 Wizard-Server kernel: aperture_remove_conflicting_pci_devices+0x1e/0x82 Dec 16 11:57:06 Wizard-Server kernel: i915_driver_probe+0x83f/0xc19 [i915] Dec 16 11:57:06 Wizard-Server kernel: ? slab_free_freelist_hook.constprop.0+0x3b/0xaf Dec 16 11:57:06 Wizard-Server kernel: local_pci_probe+0x3d/0x81 Dec 16 11:57:06 Wizard-Server kernel: pci_device_probe+0x197/0x1eb Dec 16 11:57:06 Wizard-Server kernel: ? sysfs_do_create_link_sd+0x71/0xb7 Dec 16 11:57:06 Wizard-Server kernel: really_probe+0x115/0x282 Dec 16 11:57:06 Wizard-Server kernel: __driver_probe_device+0xc0/0xf2 Dec 16 11:57:06 Wizard-Server kernel: driver_probe_device+0x1f/0x77 Dec 16 11:57:06 Wizard-Server kernel: ? __device_attach_driver+0x97/0x97 Dec 16 11:57:06 Wizard-Server kernel: __driver_attach+0xd7/0xee Dec 16 11:57:06 Wizard-Server kernel: ? __device_attach_driver+0x97/0x97 Dec 16 11:57:06 Wizard-Server kernel: bus_for_each_dev+0x6e/0xa7 Dec 16 11:57:06 Wizard-Server kernel: bus_add_driver+0xd8/0x1d0 Dec 16 11:57:06 Wizard-Server kernel: driver_register+0x99/0xd7 Dec 16 11:57:06 Wizard-Server kernel: i915_init+0x1f/0x7f [i915] Dec 16 11:57:06 Wizard-Server kernel: ? 0xffffffffa2257000 Dec 16 11:57:06 Wizard-Server kernel: do_one_initcall+0x82/0x19f Dec 16 11:57:06 Wizard-Server kernel: ? kmalloc_trace+0x43/0x52 Dec 16 11:57:06 Wizard-Server kernel: do_init_module+0x4b/0x1d4 Dec 16 11:57:06 Wizard-Server kernel: __do_sys_init_module+0xb6/0xf9 Dec 16 11:57:06 Wizard-Server kernel: do_syscall_64+0x68/0x81 Dec 16 11:57:06 Wizard-Server kernel: entry_SYSCALL_64_after_hwframe+0x64/0xce Dec 16 11:57:06 Wizard-Server kernel: RIP: 0033:0x14e944aeadfa Dec 16 11:57:06 Wizard-Server kernel: Code: 48 8b 0d 21 20 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d ee 1f 0d 00 f7 d8 64 89 01 48 Dec 16 11:57:06 Wizard-Server kernel: RSP: 002b:00007ffe72d55f08 EFLAGS: 00000246 ORIG_RAX: 00000000000000af Dec 16 11:57:06 Wizard-Server kernel: RAX: ffffffffffffffda RBX: 0000000000468c70 RCX: 000014e944aeadfa Dec 16 11:57:06 Wizard-Server kernel: RDX: 000014e944bdfaad RSI: 00000000004b1868 RDI: 000014e943cc0010 Dec 16 11:57:06 Wizard-Server kernel: RBP: 000014e944bdfaad R08: 0000000000000007 R09: 0000000000464e80 Dec 16 11:57:06 Wizard-Server kernel: R10: 0000000000000005 R11: 0000000000000246 R12: 000014e943cc0010 Dec 16 11:57:06 Wizard-Server kernel: R13: 0000000000000000 R14: 0000000000459c30 R15: 0000000000000000 Dec 16 11:57:06 Wizard-Server kernel: </TASK> Dec 16 11:57:06 Wizard-Server kernel: Modules linked in: kvm_intel(+) znvpair(PO) i915(+) spl(O) kvm iosf_mbi drm_buddy i2c_algo_bit ttm crct10dif_pclmul crc32_pclmul drm_display_helper crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel drm_kms_helper mei_hdcp mei_pxp crypto_simd cryptd rapl intel_cstate wmi_bmof drm mpt3sas intel_uncore ahci mei_me intel_gtt i2c_i801 nvme agpgart raid_class i2c_smbus hid_apple input_leds syscopyarea r8125(O) i2c_core nvme_core scsi_transport_sas joydev mei libahci led_class sysfillrect thermal sysimgblt fb_sys_fops fan tpm_crb video tpm_tis tpm_tis_core wmi tpm backlight intel_pmc_core acpi_pad acpi_tad button unix Dec 16 11:57:06 Wizard-Server kernel: CR2: 0000000000000020 Dec 16 11:57:06 Wizard-Server kernel: ---[ end trace 0000000000000000 ]--- Dec 16 11:57:06 Wizard-Server kernel: sdg: sdg1 Dec 16 11:57:06 Wizard-Server kernel: sd 2:0:4:0: [sdg] Attached SCSI disk Dec 16 11:57:06 Wizard-Server kernel: RIP: 0010:klist_put+0x16/0x74 Dec 16 11:57:06 Wizard-Server kernel: Code: 03 00 31 c0 48 89 03 5b 89 e8 5d 41 5c 41 5d c3 cc cc cc cc 41 55 41 54 41 89 f4 55 53 48 8b 2f 48 89 fb 48 83 e5 fe 48 89 ef <4c> 8b 6d 20 e8 d2 9b 03 00 45 84 e4 74 10 48 8b 03 a8 01 74 02 0f Dec 16 11:57:06 Wizard-Server kernel: RSP: 0018:ffffc9000103bab8 EFLAGS: 00010246 Dec 16 11:57:06 Wizard-Server kernel: RAX: ffff888135074b80 RBX: ffff888135074ba8 RCX: ffff888135074b80 Dec 16 11:57:06 Wizard-Server kernel: RDX: ffff888103c4b410 RSI: 0000000000000001 RDI: 0000000000000000 Dec 16 11:57:06 Wizard-Server kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffff829513f0 Dec 16 11:57:06 Wizard-Server kernel: R10: 00003fffffffffff R11: fefefefefefefeff R12: 0000000000000001 Dec 16 11:57:06 Wizard-Server kernel: R13: ffff8881010cc000 R14: ffff888105d19b50 R15: ffff8881010cc0d0 Dec 16 11:57:06 Wizard-Server kernel: FS: 000014e9445d8240(0000) GS:ffff88903f400000(0000) knlGS:0000000000000000 Dec 16 11:57:06 Wizard-Server kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 16 11:57:06 Wizard-Server kernel: CR2: 0000000000000020 CR3: 000000010368e000 CR4: 0000000000750ef0 Dec 16 11:57:06 Wizard-Server kernel: PKRU: 55555554 Do you have a monitor or at least a HDMI dummy plug connected to your iGPU? Please note that this is not related to my plugin.

For Windows 11 you have to use OVMF TPM. Try to type in exit ti restart the boot process. of course, you have to press any key to start the setup.

LOL, I think the devs are changing little things on purpose, only if you also tick the box "Show Players Servers" then it is visible. This is a screenshot from a fresh set up server where you can see that it is found in the server browser but only if you tick the box "Show Players Servers" in ASA at the bottom: (the screenshot is a bit convoluted, in the background you can see the container template in the foreground the running game with the server browser open, the right terminal is the log from the container and the left bottom terminal where it shows the ports that the container listens on <- don't worry about 8888 you don't have to open that) You only have to open up port 7777 UDP for ASA since it only listens on that port (you can see that in the terminal window at the bottom left, no need to open up other ports!).

I've now tried it and it is working as expected, I've attached my log: sotf.log (please note that this is a new set up instance) It seems that something is preventing your container form getting your public IP, you can look at my log (starting at line 251). Do you have any AdBlocking or something like that going on on your network? Do you have any Unifi gear <- these are known to block also outbound traffic from game servers. Maybe try to set up a second instance on your machine (don't forget to change the path to the game files and the container name) and see if that work, if that also doesn't work it must have something to do with your network setup.

Something is very wrong with you installation. Stop the container, delete the WINE64 folder and start the container again.

I will look into that tomorrow and report back.

Did you try to restart the container again as the log says?

Only English over here please. But I assume you can connect through the console as the other user who reported this. I will look into that tomorrow.

Please look at the run example over here, it looks like you are using the wrong docker tag.