ErikRedbeard

Members
  • Posts

    12
  • Joined

  • Last visited

ErikRedbeard's Achievements

Noob

Noob (1/14)

0

Reputation

  1. The game includes the 1.4.4 dedicated server files. 😀
  2. Neither confirmed or denied if it was fully abandoned. But the last update was from 2019 and this was only applied to the actual Starbound on steam not the server tools. There might come a time that it gets an update still, but who knows at this point. Also I'm pretty sure it always needed steam credentials considering you put this in the dockers description. I guess there's a reason why a lot of the other starbound server dockers avail on dockerhub don't use steamcmd and just tell you top copy the files instead. Simply said the current docker is outdated. You could change the steamcmd pull command to pull from steamid 211820 instead of 533830. It seems you need to own Starbound regardless of which steamid is used from what I can read in your docker description. I'm just informing/giving ideas at this point. I'm good with how mine runs for now.
  3. That's what I mean with blanking. Having the fields empty. Starbound's docker requires Steam credentials to download at all. Anonymous isn't allowed. But I had it working and steamcmd downloaded the 1.4.3 files. So I ended up removing the steam credentials so it skips past the steamcmd and then copied the 1.4.4 files over the 1.4.3 files. That's all I meant and makes it work running the 1.4.4 version. And considering there's not going to be any more updates to Starbound. I don't mind having to copy it in once.
  4. If you install the actual Starbound game on linux you get the same filestructure which also includes the starbound server files. It's just that the specific Dedicated Server Steam ID (533830) that you're currently using has never been updated and is at 1.4.3. But the actual Starbound Steam ID (211820) contains both the game and the serverfiles for version 1.4.4. But yeah. If you don't own Starbound itself it's hard to test. From what I can see the folder structure of both is identical. But afaik there is no legal official way to get 1.4.4 dedicated server files without owning Starbound itself. And from what I know Starbound isn't receiving any more updates. So I'm not expecting the free dedicated server tools to ever receive said update. Hence why I resorted to copying over the files from a 211820 steamcmd install and blanking the username/password in the docker. And now it's running 1.4.4 for me.
  5. Question regarding the Starbound docker. I noticed you're still using the "Starbound Dedicated Server" from steam, but this is and most likely will never get the last updated server files. "Starbound Dedicated Server" files are at version 1.4.3 "Starbound"s included server files are at version 1.4.4 With the current starbound version you get a mismatch files message upon trying to join a 1.4.3 server. I wonder if it would be possible to get either an update to the current docker, or a new docker that uses the actual "Starbound" steamid instead of the Dedicated Server one? I've manually fixed it for myself, by just copying over the serverfiles.
  6. Solved My issue turned out to be this and removing the resolver.conf and having it regenerate fixed my issue. Old message I'm having an issue I can't find much about. My custom docker network isn't properly doing auto dns. So far I've followed and adjusted some things based on How to Setup and Configure a Reverse Proxy on unRAID with LetsEncrypt & NGINX since it's mostly the same. NGINX is working from what I can tell. I can access www.subdomain.duckdns.org without any issues. I'm trying to get Emby configured. So I've made an emby.subdomain.conf in the proxy folder based on the sample. However the above does not work. [error] 495#495: *1 linuxserver-emby could not be resolved (110: Operation timed out), client: 192.168.1.1, server: emby.*, request: "GET / HTTP/2.0", host: "emby.subdomain.duckdns.org" If I however use the unraid or the container specific IP instead of my container name it works without issues. If I open the console for the swag container and do a "ping linuxserver-emby" it returns properly An "nslookup linuxserver-emby" comes back with Server: 127.0.0.11 Address: 127.0.0.11:53 Non-authoritative answer: *** Can't find linuxserver-emby: No answer Non-authoritative answer: Name: linuxserver-emby Address: 172.18.0.2 I'll also include my "docker network inspect bridge-dnsres" output. As that is the custom network I made with "docker network create" I'm completely stumped at this point as to why NGINX refuses to see the emby container by name.
  7. Having an issue that I noticed after last update. If an installer gives me a popup window for which branch to install none of the branches work. I can click any of the branches, but nothing at all will happen, the popup even stays open. Steps I did when issue appeared - Installed overseerr - linuxserver docker - Removed overseerr - linuxserver docker - Updated CA to last version (2021.08.08) as per CA's request - Tried installing overseerr - linuxserver docker but my above issue started appearing Any that don't give this popup work completely normal and instantly bring me to the template. It doesn't matter if it's one I've had/have installed before or if it's a completely new one. Restarting UNRAID did not solve the issue. As an example I put a picture of emby - linuxserver (one of the ones I've tried) to show what popup I mean.
  8. Ended up resorting to removing the docker.img and creating a new one and reinstalling all the dockers. This solved the issue for me. Looked to me like there was a rogue network that didn't even show up with "docker network ls".
  9. Can't get docker to see network type br0. br0 works fine for my VMs (which is the main reason I use it), but I also want one of my dockers to have it's own dedicated IP on my local network through br0. I've been trying to get my docker to see the br0 bridge, but it keeps erroring on the br0 interface. If I disable br0 and run either bond0 or eth0 as a custom network they work without issues and show up under the dockers as network type. This error appears when I start docker with br0 as a custom network: Sep 10 14:38:14 UNRAID-Redbeard rc.docker: Error response from daemon: network dm-3fedf868ec10 is already using parent interface br0 My question is if anyone has any idea how to progress from here to get docker working with the br0 network. I'm including my network settings, docker settings and part of the log when starting docker. System Log (docker start only): Sep 10 14:38:10 UNRAID-Redbeard ool www[9139]: /usr/local/emhttp/plugins/dynamix/scripts/emcmd 'cmdStatus=Apply' Sep 10 14:38:10 UNRAID-Redbeard emhttpd: Starting services... Sep 10 14:38:10 UNRAID-Redbeard emhttpd: shcmd (4000): /etc/rc.d/rc.samba restart Sep 10 14:38:10 UNRAID-Redbeard winbindd[6022]: [2020/09/10 14:38:10.476434, 0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler) Sep 10 14:38:10 UNRAID-Redbeard winbindd[6024]: [2020/09/10 14:38:10.476438, 0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler) Sep 10 14:38:10 UNRAID-Redbeard winbindd[6024]: Got sig[15] terminate (is_parent=0) Sep 10 14:38:10 UNRAID-Redbeard winbindd[6022]: Got sig[15] terminate (is_parent=1) Sep 10 14:38:10 UNRAID-Redbeard winbindd[7186]: [2020/09/10 14:38:10.476861, 0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler) Sep 10 14:38:10 UNRAID-Redbeard winbindd[7186]: Got sig[15] terminate (is_parent=0) Sep 10 14:38:12 UNRAID-Redbeard root: Starting Samba: /usr/sbin/smbd -D Sep 10 14:38:12 UNRAID-Redbeard root: /usr/sbin/wsdd Sep 10 14:38:12 UNRAID-Redbeard smbd[9578]: [2020/09/10 14:38:12.629945, 0] ../../lib/util/become_daemon.c:135(daemon_ready) Sep 10 14:38:12 UNRAID-Redbeard smbd[9578]: daemon_ready: daemon 'smbd' finished starting up and ready to serve connections Sep 10 14:38:12 UNRAID-Redbeard root: /usr/sbin/winbindd -D Sep 10 14:38:12 UNRAID-Redbeard winbindd[9591]: [2020/09/10 14:38:12.661067, 0] ../../source3/winbindd/winbindd_cache.c:3203(initialize_winbindd_cache) Sep 10 14:38:12 UNRAID-Redbeard winbindd[9591]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Sep 10 14:38:12 UNRAID-Redbeard winbindd[9591]: [2020/09/10 14:38:12.661409, 0] ../../lib/util/become_daemon.c:135(daemon_ready) Sep 10 14:38:12 UNRAID-Redbeard winbindd[9591]: daemon_ready: daemon 'winbindd' finished starting up and ready to serve connections Sep 10 14:38:12 UNRAID-Redbeard emhttpd: shcmd (4013): /usr/local/sbin/mount_image '/mnt/user/Docker/docker.img' /var/lib/docker 20 Sep 10 14:38:12 UNRAID-Redbeard kernel: BTRFS info (device loop2): using free space tree Sep 10 14:38:12 UNRAID-Redbeard kernel: BTRFS info (device loop2): has skinny extents Sep 10 14:38:12 UNRAID-Redbeard kernel: BTRFS info (device loop2): enabling ssd optimizations Sep 10 14:38:12 UNRAID-Redbeard root: Resize '/var/lib/docker' of 'max' Sep 10 14:38:12 UNRAID-Redbeard emhttpd: shcmd (4015): /etc/rc.d/rc.docker start Sep 10 14:38:12 UNRAID-Redbeard root: starting dockerd ... Sep 10 14:38:14 UNRAID-Redbeard rc.docker: Error response from daemon: network dm-3fedf868ec10 is already using parent interface br0 Sep 10 14:38:14 UNRAID-Redbeard kernel: device br0 entered promiscuous mode
  10. It is indeed gone after rebooting the system. Strange though, since I rebooted it before and it reappeared. And I didn't do anything special this time around. Either way, Thank you for your assistance. 😁
  11. Doesn't seem like there is a hassio network by running that command in the terminal. This is the output. I did however find it in here. I don't know how to go from there though.
  12. I'm having this strange issue of a route I'm unable to delete. I assume it came from a hassio docker, but I'm not sure there. And the log message after pressing delete. There's no HassIO docker installed anymore. And even with docker turned off I can't remove it.