Tuxx

Unfortunately, I couldn’t tell you. I enjoyed the synology so much I went out and bought a 915+. Now I’m moving on again to unraid.

It’s all good, I appreciate everything the community does. NIC is an easy fix if that’s all it is. Part is already in the mail. Will report back when I confirm it’s working. I ordered the Intel EXPI9301CT. Based on everything I read it seems compatible / recommended.

- Outcome of the update: FAILED - DSM version prior to update: uncertain...~DSM 6.1 - Upgrading to DSM 6.2.2-24922 - Loader version and model: Jun v1.04b - DS918 - Using custom extra.lzma: NO - Installation type: Baremetal on Asrock Q1900DC-ITX with built in Realtek RTL8111GR I upgraded DSM in the GUI, and afterwards the xpenology box is not coming back online. It looks like it runs through the bootloader just fine. But it never seems to pull an IP address and get back online. I checked from the router device listing, and the xpenology box is not pulling an IP. The xpenology box has a static IP. I tried to SSH that the network connection seems to be down as well. What did I do wrong? Any words of wisdom? Would installing an Intel NIC solve the problem?

well.... i have no clue why. but i left the house, came back a few hours later, and the plex container was showing up on the network, and plex app fully working. Not going to look a gift horse in the mouth. I guess it maybe just needed some time after container launch to spool up? Who knows. Thank you guys!

Alright... So i went nuclear. Flattened everything. Started from scratch and trying Plex first since the config is typically very simple. Found this guide ( https://blog.rylander.io/2016/11/19/install-plex-on-synology-nas-using-docker/ ), and ripped through it. Some of the screenshots are a little outdated, but generally worked well. Left off the variables he recommended for timezone / version, because they seemed outdated and inapplicable. Only problem - went to launch and host port 1900 and 5353 were already in use creating errors in the log. I switched them to host port 53530/19000 in the container settings. Was able to successfully launch with no errors. Now, I'm able to access the web interface for plex like normal. The problem is it doesn't seem to be locating my server. I.e. there is no server tab in the settings section, where i'm able to point it at my media folders etc. I'm assuming this might be linked to my ports change. Thoughts?

Is any of that editable from the gui? I'm not anti command line, but I've already installed the container from the gui, and sounds like I simply need to edit some of the settings. However - I don't see anywhere in the GUI where I can adjust those settings. If it's simply a limitation of the gui, I'll trash the container, and start from scratch. Please advise.

Started digging into the network section of dockers. Figured maybe the bridge wasn’t setup correctly because the IP wasn’t working as you suggested. Strangely enough....I was able to contact the NZBGet server IP if I used the internal port. Ie connecting on default port 6789 results in timeout. But connecting on port 32772 actually pulls up the NZBGET config screen? I’m so confused how that’s happening.

Does anyone have a dockers101 guide that is accurate? I’ve been using Synocommunity for the longest time for all my htpc software - Nzbget, sonarr, radarr, etc. I tried installing dockers, and found the packages in the repository search from Linuxserver. However that’s about as far as I got. It says the docker is running, but I couldn’t access the nzbget webpage to customize the settings or anything. Thank you for any insight / direction!

Problem solved. I had some kind of faulty upgrade that made the whole system flakey. I enabled ssh, logged in, and ran this commands: sudo /usr/syno/sbin/./synodsdefault --reinstall sudo reboot that wiped all setiings and forced a full reinstall of DSM software. Simply went to find.synology.com and followed prompts to reinstall latest DSM. All problems fixed.

- Outcome of the installation/update: UNSUCCESSFUL - DSM version prior update: 6.2.1-23824 Update 1 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock Q1900DC-ITX I’ve been using this setup for years. Occasionally upgrading, but generally content with it as is. Yesterday I decided to get my system up to speed. Went from 6.1 to 6.2, and switched to the new 1.04b boot loader. Installed the docker app and a handful of things from the repository. Basically plex, sonarr, radarr etc. trying to get on the more modern platform than synocommunity based on what I’ve been reading here. Problems I’ve encountered so far: 1- All the apps I had installed before these changes no longer load at startup. When I go into the package center I can see them in the installed package area. If I run them, they run for a while but they revert to stopped randomly. Usually very quickly. I couldn’t make it through a movie on plex yesterday. Had to start the app twice. Is this some kind of conflict between synocommunity and docker? I didn’t use docker at all just installed it to start playing around. 2- I can no longer login to the syno interface from chrome. I can only get it to login and go to the desktop mode in MS Edge. Very strange. When I upgraded bootloaders I used notepad++ to add vid and pod, then burned the image to usb stick with Rufus. Win32imager wouldn’t work for some reason. Thoughts?