Closed develroo closed 7 months ago
Hi, thanks for the info. I think I found the bug and will try to release a fix later today.
Thanks for that. Tested with existing 1.44 build. I will upgrade to 2.x at some point and make a new domain appended with api.kanka.domain.com and point to the same host. Hopefully that will work as intended too.
Cheers once again.
You shouldn't need a subdomain, that's a special case for kanka.io. the module will always append /api/1.0 of it is missing. But you should update to 2.0, because I don't actively support kanka versions older than the one on kanka.io.
develroo @.***> schrieb am Sa., 18. Nov. 2023, 13:30:
Thanks for that. Tested with existing 1.44 build. I will upgrade to 2.x at some point and make a new domain appended with api.kanka.domain.com and point to the same host. Hopefully that will work as intended too.
Cheers once again.
— Reply to this email directly, view it on GitHub https://github.com/eXaminator/kanka-foundry/issues/123#issuecomment-1817496469, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVBR7EIDSYKII4K6VPZDLLYFCS7XAVCNFSM6AAAAAA7OIU2MKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXGQ4TMNBWHE . You are receiving this because you modified the open/close state.Message ID: @.***>
Actually looking at the change log I see there might have been a change in the API url to
api.kanka.io
Given the self-hosted guide here, there needs to be another field for an api server. Or maybe a checkbox if he api server is the same server.
The effect is an error when I logged into that campaign, with the updated module, and now it shows no campaigns at all even though the API key is valid?
This is how it looks on the web server side.
[16/Nov/2023:10:34:46 +0000] [kanka.self.hosted [Remote_Addr: a.b.c.d] - - - kanka.self.hosted to: 172.19.0.7:80: "OPTIONS /1.0/api/1.0/campaigns HTTP/2.0" 404 3494 "https://fvtt.self.hosted:30000/" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/119.0"
Thanks for your attention.