CORS seems to be kept enabled for Portainer after removing the custom service.

[schumi2004]

I tried to fetch data from my portainer instance using the custom service. Eventually played with CORS headers without luck so i tried to revert the config but now my item in homer dashboard keeps adding the portainer fqdn behind the one from homer, like this:

https://homer.mydomain.com/portainer.mydomain.com

No matter what i do it keep doing this.

Tried multiple browsers already, cleard cache etc but it won't revert back to like it is configured.

  - name: "Portainer"
    logo: "assets/icons/tools/portainer.png"
    subtitle: "Hybrid & multi-cloud container management platform"
    url: "https:/portainer.mydomain.com"
    tag: "tools"
    target: "_blank"

I had other custom services configured like this but they all reverted back to normal but not for portainer.

Any ideas?

[SirMartin]

I have issues also configuring portainer with the apikey. I got CORS issue, and it is the only one. Works fine for Sonarr, Radarr, PiHole, etc.

[bursaar]

I think it's because you only have one / after the https: in the url.