Skip to content

Komf chrome extension forces https, causing fetch to fail #267

@EpicKnarvik97

Description

@EpicKnarvik97

Using the komf chrome extension, I have added the domain of my kavita instance (https://books.[REDACTED].net).
I have provided the komf settings panel with the correct local address of http://192.168.1.111:8085.
The problem is this error:

content.js:2  GET https://192.168.1.111:8085/api/config net::ERR_SSL_PROTOCOL_ERROR
io.ktor.client.fetch.fetch_$external_fun @ content.js:2
$func13167 @ e638355bd5a48a0a9411.wasm:0x39534f
$func13156 @ e638355bd5a48a0a9411.wasm:0x39462a
$func12830 @ e638355bd5a48a0a9411.wasm:0x380faf
$func2024 @ e638355bd5a48a0a9411.wasm:0x1948e2
$func2015 @ e638355bd5a48a0a9411.wasm:0x19441b
$func3884 @ e638355bd5a48a0a9411.wasm:0x1dcd5e
$func3988 @ e638355bd5a48a0a9411.wasm:0x1dfd30
$func4045 @ e638355bd5a48a0a9411.wasm:0x1e0dae
$__callFunction____->Unit_ @ e638355bd5a48a0a9411.wasm:0x192cfe
(anonymous) @ content.js:2
Promise.then
(anonymous) @ content.js:2
kotlinx.coroutines.__callJsClosure_(()->Unit) @ content.js:2
$func4048 @ e638355bd5a48a0a9411.wasm:0x1e0e0d
$func3987 @ e638355bd5a48a0a9411.wasm:0x1dfc3b
$func3977 @ e638355bd5a48a0a9411.wasm:0x1df938
$func4022 @ e638355bd5a48a0a9411.wasm:0x1e066d
$func3880 @ e638355bd5a48a0a9411.wasm:0x1dcaa6
$func3876 @ e638355bd5a48a0a9411.wasm:0x1dc6bf
$func3896 @ e638355bd5a48a0a9411.wasm:0x1dd21a
$func3299 @ e638355bd5a48a0a9411.wasm:0x1c5a67
$func3300 @ e638355bd5a48a0a9411.wasm:0x1c5bd3
$func3301 @ e638355bd5a48a0a9411.wasm:0x1c5bfe
$func8689 @ e638355bd5a48a0a9411.wasm:0x29b8ba
$func3880 @ e638355bd5a48a0a9411.wasm:0x1dcaa6
$func3876 @ e638355bd5a48a0a9411.wasm:0x1dc6bf
$func3896 @ e638355bd5a48a0a9411.wasm:0x1dd21a
$func3299 @ e638355bd5a48a0a9411.wasm:0x1c5a67
$func3300 @ e638355bd5a48a0a9411.wasm:0x1c5bd3
$func3301 @ e638355bd5a48a0a9411.wasm:0x1c5bfe
$func10138 @ e638355bd5a48a0a9411.wasm:0x2e79bc
$func7394 @ e638355bd5a48a0a9411.wasm:0x2685c6
$func7394 @ e638355bd5a48a0a9411.wasm:0x26855c
$func7394 @ e638355bd5a48a0a9411.wasm:0x26855c
$func7394 @ e638355bd5a48a0a9411.wasm:0x26855c
$func8659 @ e638355bd5a48a0a9411.wasm:0x299357
$func8775 @ e638355bd5a48a0a9411.wasm:0x29f870
$func8589 @ e638355bd5a48a0a9411.wasm:0x294800
$func8877 @ e638355bd5a48a0a9411.wasm:0x2a3380
$func8869 @ e638355bd5a48a0a9411.wasm:0x2a29e8
$func9086 @ e638355bd5a48a0a9411.wasm:0x2b22a5
$func9083 @ e638355bd5a48a0a9411.wasm:0x2b1e47
$__callFunction___Js_->Unit_ @ e638355bd5a48a0a9411.wasm:0x1e1156
(anonymous) @ content.js:2
content.js:2 ERROR: [] catching(Error: Fail to fetch), Caused by: 'Fail to fetch', Caused by: 'Error from javascript[TypeError: Failed to fetch].'
io.github.oshai.kotlinlogging.consoleError @ content.js:2
$func11936 @ e638355bd5a48a0a9411.wasm:0x350fd2
$func17388 @ e638355bd5a48a0a9411.wasm:0x5124a1
$func17392 @ e638355bd5a48a0a9411.wasm:0x512986
$func17870 @ e638355bd5a48a0a9411.wasm:0x54da79
$func2015 @ e638355bd5a48a0a9411.wasm:0x19441b
$func3884 @ e638355bd5a48a0a9411.wasm:0x1dcd87
$func3988 @ e638355bd5a48a0a9411.wasm:0x1dfd30
$func4045 @ e638355bd5a48a0a9411.wasm:0x1e0dae
$__callFunction____->Unit_ @ e638355bd5a48a0a9411.wasm:0x192cfe
(anonymous) @ content.js:2
Promise.then
(anonymous) @ content.js:2
kotlinx.coroutines.__callJsClosure_(()->Unit) @ content.js:2
$func4048 @ e638355bd5a48a0a9411.wasm:0x1e0e0d
$func3987 @ e638355bd5a48a0a9411.wasm:0x1dfc3b
$func3977 @ e638355bd5a48a0a9411.wasm:0x1df938
$func3880 @ e638355bd5a48a0a9411.wasm:0x1dcaa6
$func3341 @ e638355bd5a48a0a9411.wasm:0x1c742f
$func3343 @ e638355bd5a48a0a9411.wasm:0x1c75cc
$func3334 @ e638355bd5a48a0a9411.wasm:0x1c6f5d
$func13166 @ e638355bd5a48a0a9411.wasm:0x395335
$__callFunction___Js_->Js?_ @ e638355bd5a48a0a9411.wasm:0x192f91
(anonymous) @ content.js:2
Promise.then
kotlin.js.then_$external_fun_1 @ content.js:2
$func1925 @ e638355bd5a48a0a9411.wasm:0x192f3e
$func13156 @ e638355bd5a48a0a9411.wasm:0x3946f7
$func12830 @ e638355bd5a48a0a9411.wasm:0x380faf
$func2024 @ e638355bd5a48a0a9411.wasm:0x1948e2
$func2015 @ e638355bd5a48a0a9411.wasm:0x19441b
$func3884 @ e638355bd5a48a0a9411.wasm:0x1dcd5e
$func3988 @ e638355bd5a48a0a9411.wasm:0x1dfd30
$func4045 @ e638355bd5a48a0a9411.wasm:0x1e0dae
$__callFunction____->Unit_ @ e638355bd5a48a0a9411.wasm:0x192cfe
(anonymous) @ content.js:2
Promise.then
(anonymous) @ content.js:2
kotlinx.coroutines.__callJsClosure_(()->Unit) @ content.js:2
$func4048 @ e638355bd5a48a0a9411.wasm:0x1e0e0d
$func3987 @ e638355bd5a48a0a9411.wasm:0x1dfc3b
$func3977 @ e638355bd5a48a0a9411.wasm:0x1df938
$func4022 @ e638355bd5a48a0a9411.wasm:0x1e066d
$func3880 @ e638355bd5a48a0a9411.wasm:0x1dcaa6
$func3876 @ e638355bd5a48a0a9411.wasm:0x1dc6bf
$func3896 @ e638355bd5a48a0a9411.wasm:0x1dd21a
$func3299 @ e638355bd5a48a0a9411.wasm:0x1c5a67
$func3300 @ e638355bd5a48a0a9411.wasm:0x1c5bd3
$func3301 @ e638355bd5a48a0a9411.wasm:0x1c5bfe
$func8689 @ e638355bd5a48a0a9411.wasm:0x29b8ba
$func3880 @ e638355bd5a48a0a9411.wasm:0x1dcaa6
$func3876 @ e638355bd5a48a0a9411.wasm:0x1dc6bf
$func3896 @ e638355bd5a48a0a9411.wasm:0x1dd21a
$func3299 @ e638355bd5a48a0a9411.wasm:0x1c5a67
$func3300 @ e638355bd5a48a0a9411.wasm:0x1c5bd3
$func3301 @ e638355bd5a48a0a9411.wasm:0x1c5bfe
$func10138 @ e638355bd5a48a0a9411.wasm:0x2e79bc
$func7394 @ e638355bd5a48a0a9411.wasm:0x2685c6
$func7394 @ e638355bd5a48a0a9411.wasm:0x26855c
$func7394 @ e638355bd5a48a0a9411.wasm:0x26855c
$func7394 @ e638355bd5a48a0a9411.wasm:0x26855c
$func8659 @ e638355bd5a48a0a9411.wasm:0x299357
$func8775 @ e638355bd5a48a0a9411.wasm:0x29f870
$func8589 @ e638355bd5a48a0a9411.wasm:0x294800
$func8877 @ e638355bd5a48a0a9411.wasm:0x2a3380
$func8869 @ e638355bd5a48a0a9411.wasm:0x2a29e8
$func9086 @ e638355bd5a48a0a9411.wasm:0x2b22a5
$func9083 @ e638355bd5a48a0a9411.wasm:0x2b1e47
$__callFunction___Js_->Unit_ @ e638355bd5a48a0a9411.wasm:0x1e1156
(anonymous) @ content.js:2

The problem seems to be that the extension for whatever reason always connects to the komf URL using https.
The URL in question is only available through HTTP on the local network, and I've specificly chosen the URL as http.
If I actually go to the url I provided it, I see the configuration JSON as expected.'

I did not have any such problems while I used the old Tampermonkey script.
Komf isn't, and isn't supposed to be, public, so I cannot just proxy myself around the problem.
I have tried two up-to-date chromium-based web-browser (+ LibreWolf, but komf just shows a white square, so I couldn't even configure the extension), and they act the same, even with all extensions disabled and secure connection upgrade disabled in the browser.

As a side note, I was unsure where to report this issue I'm having, as the chrome extension store lists https://github.com/Snd-R/Komelia/issues as the support url, which seems to be a different project entirely.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions