IPLD explorer uses gateway port 8080 even if it is set to something else

[kotenok2000]

Describe the bug
I have something else running on port 8080 and have set gateway port to 8081 IPLD explorer still uses port 8080
To Reproduce
Steps to reproduce the behavior:

1. Run a web server on port 8080.
2. Start Ipfs Desktop.
3. See "Port is busy" error.
4. Press "Use port 8081 instead"
5. Set Local Gateway to use port 8081 in Ipfs Companion
6. Attempt to explore "Project Apollo Archives"
   Expected behavior
   A clear and concise description of what you expected to happen.

Screenshots

Desktop (please complete the following information):

• OS: Windows 11
• Browser Microsoft Edge
• Version 132.0.2957.140

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[welcome]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.tech if you just need general support.

[qquique]

I got this issue also, so I dig in the code and found that:

IPFS Companion doesn't modify any value of the local storage of the WebUI, so is not related to the issue.

IPFS WebUI saves this default settings of the kubo gateway when is local inside the local storage of the web browser :
"{ trustlessBlockBrokerConfig: { init: { allowLocal: true, allowInsecure: false }"

ipfs-webui/src/bundles/ipfs-provider.js

Lines 327 to 334 in 546d20a

	const kuboGateway = readSetting('kuboGateway')
	if (kuboGateway === null || typeof kuboGateway === 'string' || typeof kuboGateway === 'boolean' || typeof kuboGateway === 'number') {
	// empty or invalid, set defaults
	await writeSetting('kuboGateway', { trustlessBlockBrokerConfig: { init: { allowLocal: true, allowInsecure: false } } })
	} else if (/** @type {Record<string, any>} */(kuboGateway).trustlessBlockBrokerConfig == null) {
	// missing trustlessBlockBrokerConfig, set defaults
	await writeSetting('kuboGateway', { ...kuboGateway, trustlessBlockBrokerConfig: { init: { allowLocal: true, allowInsecure: false } } })
	}

It doesn't add "host" or "port" that are defaults that ipfs providers / helia uses it to show the Explorer page items and it fails.
https://github.com/ipfs/ipld-explorer-components/blob/c82d7bec376779e194d4c19c9d5afddcdd5d9427/src/providers/helia.tsx#L17-L29

A quick test/workaround is enabling Web Developer Tools in the browser example: Chrome

• Go to Application / Local Storage / Url of IPFS WebUI
• Modify the entry kuboGateway and add : {"host":"kubehost","port":"kubegatewayport"... leave all the rest}
• CTRL + F5, Test again the Explorer Page