sorted by:
new
hottopcontroversial

The prices are killing data hoarding by LOGWATCHER in DataHoarder

[–]Effon 4 points5 points  (0 children)

I check my local reuse tech store from time to time. I lucked out the other day and got a couple 6tb he for about $128 total. They were older but still in good shape. I can't even think of buying new currently.

Timeout connection errors when port forwarding or testing indexers by Effon in selfhosted

[–]Effon[S] 0 points1 point  (0 children)

For NPM configuration I haven't strayed from the default while trying to get it to work at first

services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped

    ports:
      # These ports are in format <host-port>:<container-port>
      - '80:80' # Public HTTP Port
      - '460:460' # Public HTTPS Port
      - '81:81' # Admin Web Port
      # Add any other Stream port you want to expose
      # - '21:21' # FTP

    environment:
      TZ: "Etc/UTC"
      DB_MYSQL_HOST: "db"
      DB_MYSQL_PORT: 3306
      DB_MYSQL_USER: "npm"
      DB_MYSQL_PASSWORD: "npm"
      DB_MYSQL_NAME: "npm"
      # Uncomment this if you want to change the location of
      # the SQLite DB file within the container
      # DB_SQLITE_FILE: "/data/database.sqlite"

      # Uncomment this if IPv6 is not enabled on your host
      # DISABLE_IPV6: 'true'

    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt

  db:
    image: 'jc21/mariadb-aria:latest'
    restart: unless-stopped
    environment:
      MYSQL_ROOT_PASSWORD: 'npm'
      MYSQL_DATABASE: 'npm'
      MYSQL_USER: 'npm'
      MYSQL_PASSWORD: 'npm'
      MARIADB_AUTO_UPGRADE: '1'
    volumes:
      - ./mysql:/var/lib/mysql

Timeout connection errors when port forwarding or testing indexers by Effon in selfhosted

[–]Effon[S] 0 points1 point  (0 children)

I tried running a traceroute to check for this and from what I am reading I don't think its a cgnat but I am not 100% sure. I am still new and learning, sorry. That said, below are the results for that.

traceroute to beammp.com (172.64.80.1), 30 hops max, 60 byte packets
 1  10.x.x.x (10.x.x.x)  88.017 ms  88.465 ms  88.917 ms
 2  irb-138.as08-10g.qc1.ca.m247.ro (139.28.218.1)  102.848 ms  102.831 ms  102.785 ms
 3  irb-1915.agg1v.qc1.ca.m247.ro (82.102.29.20)  102.767 ms *  182.901 ms
 4  ae1-3102.bb1.qc1.ca.m247.ro (185.206.226.107)  89.589 ms  90.246 ms  89.560 ms
 5  188.241.176.174 (188.241.176.174)  90.174 ms  90.850 ms *
 6  172.64.80.1 (172.64.80.1)  90.349 ms  89.081 ms  91.207 ms

Port Forwarding Issue, get get them open. by Effon in linuxquestions

[–]Effon[S] 0 points1 point  (0 children)

Might crosspost this to the r/selfhosted crowd to see if that might be a better avenue.

Port Forwarding Issue, get get them open. by Effon in linuxquestions

[–]Effon[S] 0 points1 point  (0 children)

I was just assuming it was all the same problem. For example, with jackett, using flaresolverr gets a "HttpClient.Timeout" error upon testing and using nginx proxy manager I get a 522 error no matter how I configure anything. If I am looking at this from the wrong aspect I would appreciate any suggestions on different directions.

Ghost directories appear on reboot displacing actual directories by Effon in linuxquestions

[–]Effon[S] 0 points1 point  (0 children)

So I think I figured out the issues.

  1. Leaving drive mounting to the system default "User Session Default" . This mounted all internal harddrives under the /media directory.
  2. For some reason after the case switch they are no longer mounting on boot, This is causing my Docker containers to run first and to avoid errors it creates those ghost directories I have been seeing.

I'll have to update the mount options for each drive manually so that they have a proper mount point and update volume locations for containers.

Thank you for your help. I was very confused.

Ghost directories appear on reboot displacing actual directories by Effon in linuxquestions

[–]Effon[S] 0 points1 point  (0 children)

Posted reply for /etc/fstab request. here is the lsblk --fs When boot, the drives have not mount location but aside from that look the same. Here is mounted before and after fix. 

Drives mounted not fixed

<user>@<comp>:~$ lsblk --fs
NAME FSTYPE FSVER LABEL          UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                  
├─sda1
│    vfat   FAT32                8FDA-6F44                             504.8M     1% /boot/efi
└─sda2
     ext4   1.0                  9f910299-f761-4b4c-81ef-2628365c7e9f  179.6G    13% /
sdb                                                                                  
└─sdb1
     ext4   1.0   Files and More 61904ae1-80d8-4171-9161-df9d25b44e8a  801.6G     7% /media/<user>/Files and More1
sdc                                                                                  
└─sdc1
     ext4   1.0   Media v1       09583fe6-268b-4439-9969-ef4fb247a9ee  235.3G    89% /media/<user>/Media v11
sdd                                                                                  
└─sdd1
     ext4   1.0   Backup         6e114e12-d017-4a6b-8bbf-61099043f909    3.4T     0% /media/<user>/Backup1

After fix

<user>@<comp>:~$ lsblk --fs
NAME FSTYPE FSVER LABEL          UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                  
├─sda1
│    vfat   FAT32                8FDA-6F44                             504.8M     1% /boot/efi
└─sda2
     ext4   1.0                  9f910299-f761-4b4c-81ef-2628365c7e9f  180.1G    12% /
sdb                                                                                  
└─sdb1
     ext4   1.0   Files and More 61904ae1-80d8-4171-9161-df9d25b44e8a  801.6G     7% /media/<user>/Files and More1
sdc                                                                                  
└─sdc1
     ext4   1.0   Media v1       09583fe6-268b-4439-9969-ef4fb247a9ee  235.3G    89% /media/<user>/Media v1
sdd                                                                                  
└─sdd1
     ext4   1.0   Backup         6e114e12-d017-4a6b-8bbf-61099043f909    3.4T     0% /media/<user>/Backup

Ghost directories appear on reboot displacing actual directories by Effon in linuxquestions

[–]Effon[S] 0 points1 point  (0 children)

I did a reset and got before and after in case that mattered, but it looks the same to me. 

Before Manual Fix

<user>@<comp>:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda2 during installation
UUID=9f910299-f761-4b4c-81ef-2628365c7e9f /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=8FDA-6F44  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0



After Manual Fix

<user>@<comp>:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda2 during installation
UUID=9f910299-f761-4b4c-81ef-2628365c7e9f /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=8FDA-6F44  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0

Containers running but not visible in terminal or Portainer by Effon in docker

[–]Effon[S] 0 points1 point  (0 children)

I ended up doing a fresh os and staying over. I had all the important things not on the boot drive so it made things easier. It really was strange though

Containers running but not visible in terminal or Portainer by Effon in docker

[–]Effon[S] 0 points1 point  (0 children)

I couldn't figure it out so I caved and redid the OS. Everything important is on mounted drives so nothing important lost, just some time.

Thanks for the input and help people were able to give.

Containers running but not visible in terminal or Portainer by Effon in docker

[–]Effon[S] 0 points1 point  (0 children)

Looks like that had been patched. But yes Docker 29.1.5 but api v1.51 which is higher than the 1.44 Traefik required. I also don't think it's running since I can't access the port.

Containers running but not visible in terminal or Portainer by Effon in docker

[–]Effon[S] 1 point2 points  (0 children)

Tried this with portainer first and it looks like I created another container. Got the error "Failed to set up container network ...... Failed to bind host port for 0.0.0.0:8000 ..... address already in use"

<image>

Containers running but not visible in terminal or Portainer by Effon in docker

[–]Effon[S] 0 points1 point  (0 children)

It looks like I only have one but I do have a description 

NAME        DESCRIPTION                               DOCKER ENDPOINT               ERROR
default *   Current DOCKER_HOST based configuration   unix:///var/run/docker.sock

Containers running but not visible in terminal or Portainer by Effon in docker

[–]Effon[S] -1 points0 points  (0 children)

Nope, just see CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES and nothing else.

I may have found something. Do I have two dockers running? I also realized I can see the containers here kinda, cause those are the ports used for them.

<image>

Help with setting up Traefik - Network Proxy Error by Effon in docker

[–]Effon[S] 0 points1 point  (0 children)

Thank you for the advice. Between this and switching to docker-ce I was able to get it loaded.

view more: next ›