jackett not accessible

[chenks]

got an issue with Jacket. i have a clean install of Raspberry OS and LMDS. followed the instructions to set up, installed Portainer and Jackett.

Portainer is running fine, but Jackett is not accessible on http://192.168.50.8:9117/ Portainer says Jackett is running but with no IP address or port

what have i done wrong?

[GreenFrogSB]

I assume you're doing all good. Can you try to access Jackett using IP addres of your Raspberry Pi? http://host_ip:9117

On Fri 15 Jul 2022, 2:35 p.m. chenks, @.***> wrote:

got an issue with Jacket. i have a clean install of Raspberry OS and LMDS. followed the instructions to set up, installed Portainer and Jackett.

Portainer is running fine, but Jackett is not accessible on http://:9117 Portainer says Jackett is running but with no IP address or port

what have i done wrong?

[image: Screenshot 2022-07-15 133406] https://user-images.githubusercontent.com/11945919/179223929-d63c1272-121c-4f58-a0e8-54c1513cfe71.jpg

— Reply to this email directly, view it on GitHub https://github.com/GreenFrogSB/LMDS/issues/46, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARFVEPVQW5A4PQKAH2ACIQDVUFLIVANCNFSM53VO6SBQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[chenks]

sorry, not sure what happened in the opening post.

yes i am trying to access it using the IP address - http://192.168.50.8:9117, it's dead (http://192.168.50.8:9000/ works all ok for portainer) and portainer says jacket is running but with no ip address or port.

[GreenFrogSB]

Delete jackett container using Portainer. Edit docker-compose.yml file, find section responsible for jackett, make sure it is set to :latest, save the file and run docker-compose up -d --remove-orphans This wiłl rebulind container, let me know if that works any better.

On Fri 15 Jul 2022, 3:06 p.m. chenks, @.***> wrote:

sorry, not sure what happened in the opening post.

yes i am trying to access it using the IP address - http://192.168.50.8:9117, it's dead. and portainer says jacket is running but with no ip address or port.

— Reply to this email directly, view it on GitHub https://github.com/GreenFrogSB/LMDS/issues/46#issuecomment-1185526510, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARFVEPU533KQR646M4AGOL3VUFO3TANCNFSM53VO6SBQ . You are receiving this because you commented.Message ID: @.***>

[chenks]

Edit docker-compose.yml file,

this is what it currently says

  jackett:
    image: linuxserver/jackett
    container_name: jackett
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=UTC
      - AUTO_UPDATE=true #optional
      # - RUN_OPTS=<run options here> #optional
    volumes:
      - ./volumes/jackett/config:/config
      - ./downloads:/downloads
    ports:
      - 9117:9117
    restart: unless-stopped

i updated the file, rebuilt and made no difference, still same issue. it looks like the container is in boot loop, as if i keep refreshing portainer i can see the container come up (with an IP and port), then go back on, and so on.

[GreenFrogSB]

Inside LMDS folder and LMDS folder is where you cloned it from github.

On Fri 15 Jul 2022, 4:58 p.m. chenks, @.***> wrote:

Edit docker-compose.yml file,

where is this file to edit?

— Reply to this email directly, view it on GitHub https://github.com/GreenFrogSB/LMDS/issues/46#issuecomment-1185628882, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARFVEPU3TKI2PO2P722K7JDVUF4B3ANCNFSM53VO6SBQ . You are receiving this because you commented.Message ID: @.***>

[chenks]

Inside LMDS folder and LMDS folder is where you cloned it from github.

sorry, i edited my response with more details

[GreenFrogSB]

Hard fot me to help as I am on holidays and have only phone with me. Your docker-compose.yml is OK. Have you try simply restart entire Pi? I know this is a basic question and frustrating if you try already. No one else reported to me such issue latelly.

[chenks]

yes i have rebooted a few times. i went and added 2 more containers, deluge and sabnzbd, and those are also exhibiting the same issues.

the only container that appears to be working is portainer.

[GreenFrogSB]

What is your Pi model and OS?

[chenks]

currently testing it on a Pi Zero W, runing the latest Raspberry Pi OS Lite (32bit)

[GreenFrogSB]

Could you reimage SD card with 64bit Raspbian instead and try again. I have no better suggestion for now.

[chenks]

Could you reimage SD card with 64bit Raspbian instead and try again. I have no better suggestion for now.

64bit OS is not compatible with the Pi Zero W

[GreenFrogSB]

That might be the problem. Pi zero W, based on wiki has ARMv6Z (32-bit) CPU, containers are usually available for x86/64, ARMv7 and 8 platforms, sometimes just for arm with no version ie. Portainer is just ARM but Jackett is only available for x86/64, ARM7 and ARM8. This should cause problem during pull reporting that container is not valid for your platform and I do not know why pull cause no issues for you. It seems with this cpu you won't be able to use most of the containers.

[chenks]

looks like i'll need to try and get either a pi4 or pi zero w 2, although they appear to be non-existant at the moment to buy.

[chenks]

update - managed to pick up a Pi 4 Model B (2GB RAM), and all seems to be working correctly.

[chenks]

issue can be closed, issue was non-supported pi model.