Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: status check failing for portainer #1926

Open
Meierschlumpf opened this issue Jan 12, 2025 · 2 comments
Open

bug: status check failing for portainer #1926

Meierschlumpf opened this issue Jan 12, 2025 · 2 comments

Comments

@Meierschlumpf
Copy link
Member

Describe the bug

image
for whatever reason portainer fails to fetch every single time, i am using the same ip as on the old homarr where it fetches fine, i can click on it fine and it takes me to portainer, but homarr just cant "see" it?

if i have f'ed up on some of these settings or something i take that on me, but i have checked them multiple times and tried different things, non have helped, so i'm putting them as bugs for now

also why remove the internal / external ip? that was actually really nice and helped to some times fix the fetching thing some times on old homarr

Steps to reproduce

Impact

Small, only a little annoying that it shows red when opening portainer works

Additional information

Originally posted in #1920 by @CinnamonShaey
Browser used was Arc

Version

1.0.0-beta

Installation method

Docker Compose

Browser

Other (describe in "additional information")

@Meierschlumpf
Copy link
Member Author

Hey @CinnamonShaey, is the IP you specified for the portainer app reachable from inside the homarr container? If not then this is the problem. We removed the internal and external address feature to make it easier to manage and as we now only rely on it for the ping feature. We suggest instead of using an ip to use a domain if you have one and otherwise to disable the ping feature for this app

@CinnamonShaey
Copy link

For now I have disabled the ping, but I do have a domain with Cloudflare and could make a basic tunnel which might make it accessible, though I have not tested this yet, it might fix it, just hadent made it a tunnel yet cause there would be little reason for me personally to be able to access portainer outside my home, if it's not actually a bug and simply just how it's meant to work now then I have no further problems with this specific thing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants