this post was submitted on 20 Feb 2025
17 points (94.7% liked)

Selfhosted

42716 readers
410 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
17
Need some help setting up gethomepage in my server (lemmy.world)
submitted 2 days ago by spirinolas@lemmy.world to c/selfhosted@lemmy.world
10 comments fedilink hide all child comments
 

I've tried GetHomepage and while I've configured most of it I've had a few troubles due to the instructions being very incomplete and confusing.

The one problem that eluded me was setting paperlessngx widget. Worth nothing that, unlike the other services, paperlessngx is running on docker-compose on my server. While the widget detects the service, it never gets any information

Eventually it just gives an API error

# services.yaml (just the relevant part)
   
     - Paperless-ngx:
        href: http://<myserverhost:port>
        description: Document Management System
        icon: https://static-00.iconduck.com/assets.00/paperless-icon-426x512-eoik3emb.png
        server: paperless
        widget:
          type: paperlessngx
          url: http://<local-ip:port>
          token: <token-configured-inside-paperless>


    #docker.yaml

    paperless:
      host: <local-ip>
      port: <port>

I'm out of ideas. Unfortunately the only instructions are on the site and they aren't easy to follow if you're not already familiarized with docker.

you are viewing a single comment's thread
view the rest of the comments
[–] silmarine@discuss.tchncs.de 3 points 2 days ago (1 children)

Where is paperless in relation to homepage? For me i have both of them in the same docker host and same docker network on that host and with that i only need to set the paperless container name in the widget. If paperless is on another machine make sure there is no firewall blocking the port number.

[–] spirinolas@lemmy.world 2 points 1 day ago (1 children)

They are both a docker-compose on the same machine.

[–] silmarine@discuss.tchncs.de 2 points 1 day ago* (last edited 1 day ago)

Then you should be able to do like I said and it might solve whatever is happening. I also have both homepage and paperless in the same docker-compose file. If you set the container name for each container then you can just reference that in homepage widgets. For example here is my homepage and paperless:

homepage:
    image: ghcr.io/gethomepage/homepage:latest
    container_name: homepage
    restart: unless-stopped
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Berlin
    volumes:
      - /opt/docker/homepage:/app/config
      - /var/run/docker.sock:/var/run/docker.sock:ro # (optional) For docker integrations)

  paperless:
    image: ghcr.io/paperless-ngx/paperless-ngx:latest
    container_name: paperless
    restart: unless-stopped
    depends_on:
      - paperless-redis
      - postgres
    networks:
      - proxy
    user: "1000"
    environment:
      - USERMAP_UID=1000
      - USERMAP_GID=1000
      - TZ=Europe/Berlin
      - PAPERLESS_REDIS=redis://paperless-redis:6379
      - PAPERLESS_TIKA_ENABLED=1
      - PAPERLESS_TIKA_GOTENBERG_ENDPOINT=http://gotenberg:3000/
      - PAPERLESS_TIKA_ENDPOINT=http://tika:9998/
      - PAPERLESS_DBENGINE=postgresql
      - PAPERLESS_DBHOST=postgres
      - PAPERLESS_DBNAME=paperless
      - PAPERLESS_DBUSER=paperless
      - PAPERLESS_DBPASS=password
    volumes:
      - /opt/docker/paperless/data:/usr/src/paperless/data
      - /opt/docker/paperless/export:/usr/src/paperless/export
      - /opt/docker/paperless/consume:/usr/src/paperless/consume
      - /mnt/paperless:/usr/src/paperless/media

so both have conatiner_name set to the same string as the service name. And in my homepage widgets I just use the container name in the URL, example:

    - Paperless:
        icon: paperless-ngx
        href: https://paperless.local.tld/
        widget:
            type: paperlessngx
            url: http://paperless:8000/
            username: username
            password: password

This only works if they are in the same docker network. If you don't explicitly set the network for the containers and they are in the same compose file then they should be in the same network.