Moritz Heusinger
Moritz Heusinger
Probably really a problem with the squash merges..
would this maybe help us @Apollon77 https://docs.weblate.org/en/latest/admin/addons.html#squash-git-commits I have never looked into weblate tbh
hm expected that.. then we would need to activate normal merge commits at least for weblate PRs
okay fyi I also merged a noop commit previously that day
yes all fine, just an issue in communication from browser with the server, if so it is an admin issue, as it might determined the wrong address of the backend.
one question here: are you running multihost?
In the near future we will have some additional console logging, because without it is hard to say if ip is correct and what the response actually was. https://github.com/ioBroker/ioBroker.admin/pull/2386
should be fixed with 7.0.22 and above
The question is, is the upgrade really failing or just the communication to the upgrader service is broken down. Because of course admin cannot run while updating itself. But if...
In the near future we will have some additional console logging, because without it is hard to say if ip is correct and what the response actually was. https://github.com/ioBroker/ioBroker.admin/pull/2386