Kodi uses default port since it is hardcoded in addon.xml

[antonsoroko]

even if user change port - Kodi still uses default port since it is hardcoded in addon.xml

repository.github/addon.xml

Lines 8 to 10 in 26a29e3

	<info>http://127.0.0.1:61234/addons.xml</info>
	<checksum>http://127.0.0.1:61234/addons.xml.md5</checksum>
	<datadir>http://127.0.0.1:61234/</datadir>

@i96751414 is it possible to make these lines dynamic somehow? what do you think?

you can see log here elgatito/plugin.video.elementum#1117 (comment)

[i96751414]

Hi. It is not "hardcoded". When the user changes the port, that should also be updated:

repository.github/lib/service.py

Lines 19 to 25 in 26a29e3

	def update_repository_port(port, xml_path=os.path.join(ADDON_PATH, "addon.xml")):
	base_url = "http://127.0.0.1:{}/".format(port)
	tree = ElementTree.parse(xml_path)
	tree.find("extension[@point='xbmc.addon.repository']/dir/info").text = base_url + "addons.xml"
	tree.find("extension[@point='xbmc.addon.repository']/dir/checksum").text = base_url + "addons.xml.md5"
	tree.find("extension[@point='xbmc.addon.repository']/dir/datadir").text = base_url
	tree.write(xml_path, encoding="UTF-8", xml_declaration=True)

[antonsoroko]

@i96751414 hi. Interesting. But in log from user I see that Kodi is still trying to connect to old port.

[i96751414]

Please note that changes to the port only become active after restarting kodi.

[antonsoroko]

@i96751414 i just have tested it by myself.
i changed port (from 65223 to 45223), checked that addon.xml was updated , restarted kodi.
but i still see old and new port in log:

2025-05-17 15:52:29.633 T:448226 warning <general>: Repository add-on repository.elementumorg uses plain HTTP for add-on downloads in path http://127.0.0.1:45223/ - this is insecure and will make your Kodi installation vulnerable to attacks if enabled!
2025-05-17 15:52:29.634 T:448226 warning <general>: Repository add-on repository.elementumorg uses plain HTTP for add-on downloads in path http://127.0.0.1:45223/ - this is insecure and will make your Kodi installation vulnerable to attacks if enabled!
2025-05-17 15:53:24.665 T:448129 warning <general>: Repository add-on repository.elementumorg uses plain HTTP for add-on downloads in path http://127.0.0.1:45223/ - this is insecure and will make your Kodi installation vulnerable to attacks if enabled!
2025-05-17 15:53:24.687 T:448129 warning <general>: Repository add-on repository.elementumorg uses plain HTTP for add-on downloads in path http://127.0.0.1:45223/ - this is insecure and will make your Kodi installation vulnerable to attacks if enabled!
2025-05-17 15:53:24.693 T:448129 warning <general>: Repository add-on repository.elementumorg uses plain HTTP for add-on downloads in path http://127.0.0.1:45223/ - this is insecure and will make your Kodi installation vulnerable to attacks if enabled!
2025-05-17 15:53:27.260 T:448425 warning <general>: Repository add-on repository.elementumorg uses plain HTTP for add-on downloads in path http://127.0.0.1:65223/ - this is insecure and will make your Kodi installation vulnerable to attacks if enabled!
2025-05-17 15:53:29.746 T:448440 warning <general>: Repository add-on repository.elementumorg uses plain HTTP for add-on downloads in path http://127.0.0.1:65223/ - this is insecure and will make your Kodi installation vulnerable to attacks if enabled!
2025-05-17 15:53:30.504 T:448445 warning <general>: Repository add-on repository.elementumorg uses plain HTTP for add-on downloads in path http://127.0.0.1:65223/ - this is insecure and will make your Kodi installation vulnerable to attacks if enabled!

the repo works. but this old port in logs is very confusing.

[i96751414]

That's strange indeed. I guess kodi does some caching

[antonsoroko]

@i96751414 i see that Kodi stores addons metadata in userdata/Database/Addons33.db
and looks like this metadata is not updated by Kodi even if addon.xml was updated.

if i edit this metadata manually (i used "DB Browser for SQLite") - then log messages with old port disappear.

maybe there is some api/rpc call to update metadata in db, i am not sure.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[antonsoroko]

If this can't be fixed - then I guess docs should be updated about this nuance.

[i96751414]

I will eventually add some more protection methods around this - so let's keep this open to track it.