Selfhosted

60664 readers

508 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Need some help setting up gethomepage in my server (lemmy.world)

submitted 1 year ago by spirinolas@lemmy.world to c/selfhosted@lemmy.world

9 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

[–] tofubl@discuss.tchncs.de 4 points 1 year ago (1 children)

I don't think it's you. The paperless widget stopped working for me recently after it had been fine before. Similar setup to yours.

It bothered me a little but since the widget isn't actually very useful to me I didn't care to invest more time to get to the bottom of it.

[+] swerler@lemm.ee 2 points 1 year ago* (last edited 1 year ago) (1 children)

[deleted]

[–] tofubl@discuss.tchncs.de 1 points 1 year ago (1 children)

Would love to see it.

Here's mine from the Paperless compose.yml (non functional):

  webserver:
    image: ghcr.io/paperless-ngx/paperless-ngx
    [...]
    labels:
      - homepage.group=Productivity
      - homepage.name=Paperless
      - homepage.icon=paperless.png
      - homepage.href=https://[LOCAL URL]
      - homepage.description=Document Management
      - homepage.widget.type=paperlessngx
      - homepage.widget.url=http://[PAPERLESS IP:PORT]
      - homepage.widget.key=[PAPERLESS API TOKEN]

And here's the error from Homepage frontend:

    API Error: Unknown error
    URL: http://[PAPERLESS IP:PORT]/api/statistics/?format=json
    Raw Error:
    {
        "errno": -110,
        "code": "ETIMEDOUT",
        "syscall": "connect",
        "address": "[PAPERLESS IP]",
        "port": [PAPERLESS PORT]
    }

[–] Darkassassin07@lemmy.ca 1 points 1 year ago* (last edited 1 year ago) (1 children)

"code": "ETIMEDOUT"

Homepage is unable to reach the host you gave it. IP/hostname changed.

Don't use the IP of the container, use its name (which you should set in paperless' compose file: 'container_name: paperless')

[–] tofubl@discuss.tchncs.de 1 points 1 year ago

I need to use the IP for specific reasons concerning my setup; and I don't want the two containers to share a Docker network.

This used to work exactly as is when I set it up, but doesn't anymore.

I tinkered with it some more now and I found that while I can ping the docker host, I can't actually wget anything from any docker services from within the Homepage container. Currently at a loss why that might be.