API Access from https failed #1912

New Issue

twei · 2022-03-30T05:31:45Z

twei commented

2022-03-30 05:31:45 +00:00

Hi there,

I received the following error on a fresh vikunja installation.

In Chrome Developer Console

Mixed Content: The page at 'https://vikunja.example.org/api/v1/info' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://vikunja.example.org/api/v1/info'. This request has been blocked; the content must be served over HTTPS.

FWIW I set the whole thing up with traefik, docker compose and vikunja. CORS defaults to true. Perhaps you would have an idea where this issue comes from?

Hi there, I received the following error on a fresh vikunja installation. In Chrome Developer Console > Mixed Content: The page at 'https://vikunja.example.org/api/v1/info' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://vikunja.example.org/api/v1/info'. This request has been blocked; the content must be served over HTTPS. FWIW I set the whole thing up with traefik, docker compose and vikunja. CORS defaults to true. Perhaps you would have an idea where this issue comes from?

konrad commented

2022-03-30 06:01:41 +00:00

Does it work? Are you able to use the frontend?

twei commented

2022-03-30 06:10:46 +00:00

No, it didn't work, as the frontend could not communicate with the backend

konrad commented

2022-03-30 16:18:33 +00:00

Can you show your config? Did you configure an API Url in the frontend container?

twei commented

2022-03-31 03:52:13 +00:00

Sorry, upon closer inspection, chrome cached a misconfigured API frontend page, and I couldn't get it to work. However, when I switch to a different profile, it will work. Do you have any suggestion on how to clearing the cache? I unregistered the workers but it still didn't work.

konrad commented

2022-03-31 08:38:27 +00:00

If you manually changed the api URL in the frontend, it is saved in local storage. But you should be able to just change it back.

Does it work if you open the page in a private window?

If you manually changed the api URL in the frontend, it is saved in local storage. But you should be able to just change it back. Does it work if you open the page in a private window?

twei commented

2022-03-31 09:00:56 +00:00

Sadly manually changing the API URL doesn't work if I refresh the page. I have to do a hard reset in developer tools to get it working correctly.

konrad commented

2022-04-01 21:21:23 +00:00

You mean in local storage? That's where the api url is stored when manually changed.

konrad commented

2022-04-01 21:23:48 +00:00

Just to be sure we're on the same page here, you're changing the API url in the frontend here:

and then in the input field that pops up after clicking on "change" - is that correct?

Just to be sure we're on the same page here, you're changing the API url in the frontend here: ![image](/attachments/d133c1b1-1aea-4ea9-ac49-c210f90f1f61) and then in the input field that pops up after clicking on "change" - is that correct?

image.png

19 KiB

twei commented

2022-04-02 01:21:21 +00:00

exactly, yes

konrad commented

2022-04-02 07:05:27 +00:00

Can you reproduce that on try?

twei commented

2022-04-02 14:26:50 +00:00

Huh I failed to reproduce that on try. FWIW I first used the env variable VIKUNJA_API_URL to a wrong value. Then I removed the env and restarted from docker compose, but it stuck to the chrome. Firefox and safari worked fine though.

Huh I failed to reproduce that on try. FWIW I first used the env variable `VIKUNJA_API_URL` to a wrong value. Then I removed the env and restarted from docker compose, but it stuck to the chrome. Firefox and safari worked fine though.

konrad commented

2022-04-02 21:11:40 +00:00

That sounds like the problem is solved?