Mainfrezzer

Just in case somebody else runs into the issue, as i just got informed about. I do publish the pelican images on dockerhub as well. So in case github is being classic github again and wont work for updates, pelican is also available under mainfrezzer/pelican-panel:latest and mainfrezzer/pelican-wing:latest respectively

No there isnt a need to change it. It might make sense if you care about write amplification and you have a lot of container that write tiny changes within their non-mapped paths but the chances are slim for that (i hope so at least).

So i checked, in order for them to show up, they have to have the steam query port exposed/accessible from the internet. (probably mixed that up with Ascended, which does its own thing)

Clusters not showing up in the list is certainly outside of my hands as that is completely ark related, but generally without knowing the specifics it works (they should even pop up when theyre not publicly listed IIRC) For your cluster data, you also probably want to set the clusterdiroverwrite, as its probably mapped differently for each one -clusterid=CLUSTERID -ClusterDirOverride=/serverdata/serverfiles/clusterfiles (keep in mind that this are in-container paths) Ive a full repo for cluster setups which share the same install with only their save path being seperate https://github.com/Mainfrezzer/A3C Sitenote: ive to note in general, as i discovered a while ago. Enabling crossplatform play with epic breaks voice chat completely. No clue when they broke it, probably with aquatica

if you want the servers attached to your custom network, put in network_mode your custom network

yeah wing connects to the panel and then modifies the config.yml in its folder. the displayed config in the panel is just for the initial setup

if its that "empty", you didnt connect the node to the panel yet. the full file would look something along the lines of this debug: false app_name: pelican uuid: token_id: token: api: host: 0.0.0.0 port: 8080 ssl: enabled: false cert: /etc/letsencrypt/live/10.0.0.2/fullchain.pem key: /etc/letsencrypt/live/10.0.0.2/privkey.pem disable_remote_download: false remote_download: max_redirects: 10 upload_limit: 256 trusted_proxies: [] system: root_directory: /mnt/user/appdata/pelican-wing log_directory: /mnt/user/appdata/pelican-wing/log data: /mnt/user/appdata/pelican-wing/data archive_directory: /mnt/user/appdata/pelican-wing/data/archives backup_directory: /mnt/user/appdata/pelican-wing/data/backups tmp_directory: /tmp/pelican username: nobody timezone: Europe/Berlin user: rootless: enabled: false container_uid: 0 container_gid: 0 uid: 99 gid: 100 passwd: enable: true directory: /tmp/pelican machine_id: enable: true directory: /tmp/pelican/machine-id disk_check_interval: 150 activity_send_interval: 60 activity_send_count: 100 check_permissions_on_boot: true enable_log_rotate: true websocket_log_count: 150 sftp: bind_address: 0.0.0.0 bind_port: 2022 read_only: false key_only: false crash_detection: enabled: true detect_clean_exit_as_crash: true timeout: 60 crash_detection_activity_lines: 2 backups: write_limit: 0 compression_level: best_speed remove_backups_on_server_delete: true transfers: download_limit: 0 openat_mode: auto docker: network: interface: 10.16.5.1 dns: - 10.0.0.10 - 10.0.0.9 - 1.1.1.1 - 1.0.0.1 name: pelican_net ispn: false IPv6: false driver: bridge network_mode: pelican_net is_internal: false enable_icc: true network_mtu: 1500 interfaces: v4: subnet: 10.16.5.0/24 gateway: 10.16.5.1 v6: subnet: fd00:10:16:5::/64 gateway: fd00:10:16:5::1011 domainname: "" registries: {} tmpfs_size: 100 container_pid_limit: 512 installer_limits: memory: 1024 cpu: 100 overhead: override: false default_multiplier: 1.05 multipliers: {} use_performant_inspect: true userns_mode: "" system_ips: [] log_config: type: local config: compress: "false" max-file: "1" max-size: 5m mode: non-blocking throttles: enabled: true lines: 2000 line_reset_interval: 100 remote: http://10.0.0.2:8088 remote_query: timeout: 30 boot_servers_per_page: 50 custom_headers: {} allowed_mounts: [] Search: blacklisted_dirs: - node_modules - .git - .wine - appcache - depotcache - vendor max_recursion_depth: 8 BlockBaseDirMount: true allowed_origins: [] allow_cors_private_network: false ignore_panel_config_updates: false

in the wings config.yml is a section called docker. you can change the network_mode to whatever other docker network you have

This has caused severe emotional distress in me. I didn't know where to lurk, so I went outside and got a sunburn. Unacceptable. Please make it right. Thank you!

For anyone updating to the newest release of the pelican panel (as of the 22nd of june, beta35). you need to add a new mapping to your template to include plugins now https://github.com/Mainfrezzer/UnRaid-Templates/commit/310b40843ba29f1dbe4b179aefa6b7c8a54676ee

It does port forward just fine. It uses whatever mapping you use for container. So if you try to host a website in the container on port 80, but map it it 2345. It's port 2345 for the wireguard forwarding. Granted, gonna be a pain in the ass for anything dynamic but when you know what you need, it works fine. My main page and repo is hosted that way, including their proxy, as there I don't need ipv6.

Theres some posts in the discord about it, been borked for a while and seems to be somewhat browser dependent but you do get different results for each person as it appears. Dont worry about it

im not sure where you looked but its certainly 2023.11.22 https://raw.githubusercontent.com/giganode/unraid-i915-sriov/refs/heads/master/i915-sriov.plg

You actually never have to touch any of the command line, everything one could do with basic storage needs can be done completely via gui. Fuse is just the layer the array, the "unraid special", uses to combine all single array disks to one "big disk". Fuse does have its quirks but theyre well documented here. From your earlier comments, i dont know why you were playing around with the array anyway. Since you mentioned windows storage spaces, you should be aware of the performance of the "parity protected" option, it also suffers from the CMR/SMR mix (well SMR as parity device), so you must be using the raid profiles there. The pools would be the options to go there, since youre not limited by single disks speeds or the fuse overhead there. But that contradicts with what you actually want, since you seems too look for mixing disks. So im confused. And yeah its says 30 days, but you can extend 15 days for 2 times iirc, which should come up to 60 days total. Edit: You might have a look, if youre still interested in something linux, into mergerfs with snapraid. Maybe thats something for you. Works kinda the same but not really. I do use it for my backup server.

Just in case somebody happens to upgrade to 7.3.1 and experiences some funkyness with the ark container. Im aware of it looping. Im not absolutely certain as to why but i think i narrowed it down. I currently have a testbuild under the tag :test available. (includes a bump to wine11) Edit; Should be sorted via regular update