Xteve stops adding port number to 'icon src' URL of xteve.xml file after an unspecified period of time

[stevehop]

Please first read the documentation. Problems affecting the client, e.g. Plex or Emby should be reported there in the forum.

Describe the bug
After an undetermined period of time, presumably following a refresh of configured playlists, Xteve stops adding its port number (34400 in my case) to the icon URL of the generated XML file which means that clients like Plex stop displaying the channel icon in their guide. A restart of Xteve restores the port number for a period of time before it disappears again. This bug occurs for me in both v2.12 and v2.1.2.0129-beta. Have attached two screenshots, one showing the XML with the port numbers included and one taken later when the bug has occurred.

Server (please complete the following information):

• Windows
• x64
• v2.12 and v2.1.2.0129-beta

To Reproduce
Steps to reproduce the behavior:

1. Configure Xteve 'Schedule for updating (Playlist, XMLTV, Backup)'
2. Restart Xteve
3. Wait. The bug doesn't occur after manually refreshing playlist sources

Expected behavior
Xteve server port number should be included in the XML file after all refreshes

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Browser Firefox
• Version 82.03

[mar-mei]

Strange, I can't reproduce this.
If xTeVe stratet, the port is read from the settings.json to start the xTeVe web server.

The BASE_URL is regenerated with every request to the web server. This is what the Go HTTP framework does.

This is what an HTTP request looks like, the red one is the host address, this entry is used for further processing:

If you are using Windows Server there are some compatibility issues with Go

[stevehop]

It's definitely happening during the scheduled updates set within Xteve as my latest XML which was updated at 17.01, just under 2 hours after restarting Xteve, has the port missing again.

As you say @mar-mei this is Windows Server 2012 R2

I'm thinking that as a workaround I could set Xteve to use port 80, as nothing else is using that port on this server, that way the missing port number in the URL won't matter