Posts by mervincm

Quote from Phazelton78

Thanks! I had not cleared my appdata folder from the previous non vpn install, Deleted everything and its up and running now. Much appreciated!

No problem. OMV is a fun platform to play with.

I can't wait till they rev that haugene container and allow us to add our own vpn config files. I only have a limited VPN account and I can't access the range that is included for my provider and would like to tweak it.

OK I just deleted the stack, cut and pasted the text and its working, not sure what happened .. maybe I was not careful in volume cleanup? ..

hehe

OK something weird is going on. since mine is only in a lab for now, I redeployed this and I have the same issue as you. I can't connect to any of the apps in the container any more. I will let you know if I can determine why.

I am not sure. I use this container in a modified form as I have a different VPN provider, I wanted watch folders and wanted another app (sabnzbd). I believe the idea of this one was to make sure that every one of these apps only accesses the Internet via the VPN. I am not sure how easy it is to do so outside of one stack.

This is what I have used.

version: '2.1'

services:

  transmission-openvpn:

    volumes:

      - /srv/dev-disk-by-label-Vol1NVME/downloads/:/data
      
      - /srv/dev-disk-by-label-Vol1NVME/downloads/watch/:/watch

      - /etc/localtime:/etc/localtime:ro

    environment:

      - PUID=100

      - PGID=1000

      - CREATE_TUN_DEVICE=true

      - OPENVPN_PROVIDER=SLICKVPN

      - OPENVPN_CONFIG=Canada-Montreal
      
      - OPENVPN_USERNAME=name

      - OPENVPN_PASSWORD=pass

      - OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60

      - WEBPROXY_ENABLED=false

      - LOCAL_NETWORK=10.0.0.0/21

      - TRANSMISSION_SCRAPE_PAUSED_TORRENTS_ENABLED=false

      - DNS=8.8.8.8,8.8.4.4

    cap_add:

      - NET_ADMIN

    logging:

      driver: json-file

      options:

        max-size: 10m

    ports:

      - 9091:9091

      - 9117:9117

      - 7878:7878

      - 8989:8989

      - 8686:8686

      - 5299:5299
      
      - 8080:8080
      
      - 9090:9090

    restart: always

    image: haugene/transmission-openvpn

  jackett:

    image: linuxserver/jackett

    container_name: jackett

    network_mode: "service:transmission-openvpn"

    environment:

      - PUID=100

      - PGID=1000

      - TZ=America/Edmonton

      - AUTO_UPDATE=true #optional

      - RUN_OPTS=#optional

    volumes:

      - /srv/dev-disk-by-label-Vol1NVME/appdata/Jackett/:/config

      - /srv/dev-disk-by-label-Vol1NVME/downloads/completed/:/downloads

    restart: unless-stopped

  sabnzbd:

    image: linuxserver/sabnzbd

    container_name: sabnzbd

    network_mode: "service:transmission-openvpn"

    environment:

      - PUID=100

      - PGID=1000

      - TZ=America/Edmonton

    volumes:

      - /srv/dev-disk-by-label-Vol1NVME/appdata/SABnzbd/:/config

      - /srv/dev-disk-by-label-Vol1NVME/downloads/incomplete/:/incomplete-downloads
      
      - /srv/dev-disk-by-label-Vol1NVME/downloads/completed/:/downloads
      
      - /srv/dev-disk-by-label-Vol1NVME/downloads/watch/:/watch
      
    restart: unless-stopped

  radarr:

    image: linuxserver/radarr:preview

    network_mode: "service:transmission-openvpn"

    container_name: radarr

    environment:

      - PUID=100

      - PGID=1000

      - TZ=America/Edmonton

      - UMASK_SET=022 #optional

    volumes:

      - /srv/dev-disk-by-label-Vol1NVME/appdata/Radarr/:/config

      - /srv/dev-disk-by-label-Vol2R5/Media/Movies/:/movies

      - /srv/dev-disk-by-label-Vol1NVME/downloads/completed:/downloads

    restart: unless-stopped

  sonarr:

    image: linuxserver/sonarr:preview

    network_mode: "service:transmission-openvpn"

    container_name: sonarr

    environment:

      - PUID=100

      - PGID=1000

      - TZ=America/Edmonton

      - UMASK_SET=022 #optional

    volumes:

      - /srv/dev-disk-by-label-Vol1NVME/appdata/Sonarr/:/config

      - /srv/dev-disk-by-label-Vol2R5/Media/TV Shows/:/tv

      - /srv/dev-disk-by-label-Vol1NVME/downloads/completed/:/downloads

    restart: unless-stopped

  lidarr:

    image: linuxserver/lidarr

    network_mode: "service:transmission-openvpn"

    container_name: lidarr

    environment:

      - PUID=100

      - PGID=1000

      - TZ=America/Edmonton

      - UMASK_SET=022 #optional

    volumes:

      - /srv/dev-disk-by-label-Vol1NVME/appdata/Lidarr:/config

      - /srv/dev-disk-by-label-Vol2R5/Media/Music/:/music

      - /srv/dev-disk-by-label-Vol1NVME/downloads/completed/:/downloads

    restart: unless-stopped

  lazylibrarian:

    image: linuxserver/lazylibrarian

    network_mode: "service:transmission-openvpn"

    container_name: lazylibrarian

    environment:

      - PUID=100

      - PGID=1000

      - TZ=America/Edmonton

      #- DOCKER_MODS=linuxserver/calibre-web:calibre #optional

    volumes:

      - /srv/dev-disk-by-label-Vol1NVME/appdata/Lazylibrarian/:/config

      - /srv/dev-disk-by-label-Vol1NVME/downloads/completed/:/downloads

      - /srv/dev-disk-by-label-Vol2R5/Media/Novels/:/books

    restart: unless-stopped

try LOCAL_NETWORK=192.168.0.0/24

You really only need to make a single SMB share in SAMBA, it could be root of everything you access. You really don't need to open access to more of your server than that.

PS there are changes on the client side as well. Windows 10 now, by default, disabled guest access over SMB2.

https://docs.microsoft.com/en-…b2-is-disabled-by-default

I just have an id and password that I save on my windows 10 boxes, its easier than forcing the insecure options to work.

Quote from CK77

have never heard of a computer not turning on at all when you have a faulty SSD.

It could be as simple as a short from 5v to ground in the SSD. You are not using another power connector or and extender with the new ssd that was not used with the old one are you? I have seen this in cheap sata power splitters, folks have even had fires in their pc's because of these things.

Lastly, I managed to find a nic that the boot/install process does not support, (a realtek 2.5GB NIC)

So I decided to try an install with that as the only NIC. Right away it told me it didn't find a compatible NIC and to chose the driver for the network card. since you didn't see this, I don't think your network card compatibility is the issue.

The only way I was able to stimulate your issue was with an unplugged network cable.

try another one, make sure its plugged in solidly, and into a LAN port on your comcast router.

good luck!

OK, I repeated the install, this time with nothing plugged into my network port, to simulate what happens when there is no path to the DHCP server.

The install proceeded as before, but instead of asking me for the hostname, I now got a notification that network autoconfiguration had failed.

This lines up with what I suspect you saw.

So, bad cable or maybe incompatible NIC still seem possible issues.

I continued with the install choosing not to configure network at this time

I then saw the bad mirror red screen, like you did. this seems expected when network isn't functional.

I had to back out and not configure an archive mirror

the install completed and I was prompted to reboot after disconnecting the installation media, so I did.

It rebooted into OMV, so i logged in locally with root, then ran omv-firstaid, and chose option 1 to config network.

At this point it listed my intel NIC, so I know that the driver loaded and the nic is compatible with debian / omv.

I configured it to use dhcp with ipv4 and not to use ipv6 and then restarted it with the reboot command.

I then plugged in the cable, 2 seconds later i got the two beeps letting me know that OMV had started correctly.

sure enough I pinged it from another system and it responded correctly.

If you can get into omv-firstaid it will tell you if the nic was loaded correctly, even if you dont have a cable connected.

OK I just installed a fresh disk and put the latest OMV ISO on a USB boot. I told my bios to boot from USB and it did. I selected the language/KB option and it got to the point it attempts DHCP and I got a message it was successful and it is asking me for a hostname.

At this point I can already ping the OMV system (by the DHCP assigned IP address, you can get that from your comcast router) from another pc on the same network.

If you can't do the same, I would suggest that you have a cabling problem, or the NIC in your laptop might not be compatible with debian

I will dig out a couple disks and download the latest omv.iso, perhaps i can simulate what you see.

Quote from jd upgraded Pi 4

So now I am on the page that need the internet connection and that is to config the package manager. OMV wants a HTTP proxy info (blank for none) it questions me. I leave it blank.

it could not communicate with the mirror site I chose and replies to me with Bad archive mirror

it suggests I can find additional details in the /var/log/syslog I do not know how to get that specific maybe

not sure why it cut off the paste but broke it down to 2 cuts

Display More

MIMO errors are related to wireless connections, so thats not related to your issue.

You will not have an http proxy. That is typically for a corporate environment that does not provide a direct path out to the Internet.

leave it blank is correct.

If your laptop has a healthy network connection on your local network, you should be able to ping it from another system in your home. chose something also wired ethernet if possible.

Once the install is done, you will know if DHCP was the issue, and if manual ip config was the solution! I hope you are right. Next you will likely find that you used up your 500GB drive for OMV install, but one problem at a time

Not sure if this helps, but with that container, those apps will not connect till the vpn connects successfully, that's my experience anyway.

I wouldn't jump to that conclusion. DHCP is enabled as per your screen shot, and DHCP is pretty bullet proof. When it does not work, I would always start with the physical layer. Are you positive it is plugged in all the way on both the laptop NIC and on the comcast router side? Do you have a link light to show that you have a connection. Are you positive you cable is good. do you have another to swap in to make sure?

I have only installed OMV 5 or 6 times, but I have always used DHCP till install was done, then I swapped it over to manual ip config.

Can you go into your comcast modem/router's portal and then DHCP server and see if it assigned your laptop's ethernet nic an ip address? it should list a mac address and ip address pairing that you can then compare to the mac of your laptop's ethernet nic to make sure that it was the correct device and NIC.

This way you can confirm that the DHCP process completed.

I bet you are going down the wrong path looking for an older install. Make sure you are using cabled Ethernet, not wireless WiFi, this solution, by design, is not WiFi friendly.

agreed! I am still playing with it on a spare system, but so far it's excellent. Community seems to be excellent as well, folks are willing to help without the snark that has crept into some NAS communities. its given me exactly what I was looking for, a full blown linux install with an add on that removes much of the drudgery from having to do it all from scratch via command line.

tree was not installed so I did that. unfortunately more of the same. It supplies the optional "dev/srxxx" value, but not the required "dev/sgxxx" value

root@omv:~# tree /dev/disk -a

/dev/disk

├── by-id

│ ├── ata-HL-DT-ST_BD-RE_BH12LS35_K95B2RE2718 -> ../../sr0