Skip to content

Conversation

Rycochet
Copy link

Proposed change

Add note about potentially needing --api.insecure=true in the traefik config to allow the Traefik widget API access. Included a link to the official Traefik docs for how to do this and only quoted the CLI change for brevity.

Type of change

  • New service widget
  • Bug fix (non-breaking change which fixes an issue)
  • New feature or enhancement (non-breaking change which adds functionality)
  • Documentation only
  • Other (please explain)

Add note about potentially needing "api.insecure=true"
@shamoon
Copy link
Collaborator

shamoon commented Sep 10, 2025

Thanks, since this really hasn't been an issue (for anyone?) in the ~3years the widget has been around Im not going to merge this and suggest that authoritatively it should be set. I think the circumstances are specific (for example, I dont have it set and use https://traefik:443 as my url) and adding this line will potentially just create noise / confusion.

Thanks again.

@shamoon shamoon closed this Sep 10, 2025
@Rycochet Rycochet changed the title Update traefik.md Update traefik.md for note a potential API Error solution Sep 10, 2025
@Rycochet
Copy link
Author

Given that I'm not using SSL / 443 and am on the standard 8080 port - with no special arguments for the api except --api.dashboard=true it's worth noting that this is going to be the case for some people who try it and it doesn't work - and then decide simply to not use it (or spend time figuring out how to make it work) - this will be in the history if anyone checks on github at least ;-)

@shamoon
Copy link
Collaborator

shamoon commented Sep 10, 2025

Yea as a discussion might be more useful than in the docs, again given that it hasn’t really come up (I see one similar one but not exactly)

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

Successfully merging this pull request may close these issues.

2 participants