IPFS Desktop UI doesn't allow me to change the gateway used for generating shareable links
SngLol opened this issue · 8 comments
Describe the bug
IPFS Desktop UI doesn't allow me to change the gateway used for generating shareable links. This is my gateway for my own tunneled network, and I want my IPFS Desktop UI to use this when generating links so I don't have to manually change them around every single time i want to send a link to another device.
Expected behavior
To accept whatever i enter into the box, why wouldn't it?
Screenshots
Desktop :
- OS: [Windows 10]
Additional context
IPFS Desktop Revision 2277a09
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.io if you just need general support.
Thanks for submitting this issue @SngLol, this is actually by design in ipfs-webui the check does not account for port numbers, since this is expected to be a public gateway.
Hence the check translates into (e.g.): http://127.0.0.1/ipfs/bafybeibwzifw52ttrkqlikfzext5akxu7lz4xiwjgwzmqcpdzmp3n5vnbe?now=1697183725814&filename=1x1.png (missing port)
Based on your setup, there could be multiple solutions, a reverse proxy could be helpful, or since the IP range you described looks like you're running this in a docker container, you can prolly map this to "80:8080" (this might need some additional configs too).
let me know what works.
The only problem I'm having is that the IPFS Desktop UI doesn't want to use http://172.22.2.2:8080/ instead of http://ipfs.io/ when generating sharable links. I shouldn't have to reconfigure my gateway. IPFS Desktop UI should allow me to use whatever i want regardless if it thinks the gateway would work or not. the gateway works for me and only me, which is the point. Now for ease of use I want IPFS Desktop UI to simply use my gateway when generating links. Nothing should be stopping me. Yet it is. Either make it accept anything or have a line in the config file for IPFS where I can manually input any gateway for this purpose.
EDIT: Also, entering http://172.22.2.2/ doesn't work either. Port numbers is not the issue.
@SngLol does your server respond to queries on http://172.22.2.2, i.e. port 80 is forwarded to 8080?
The test is to check for http://172.22.2.2/ipfs/bafybeibwzifw52ttrkqlikfzext5akxu7lz4xiwjgwzmqcpdzmp3n5vnbe?now=1697766015133&filename=1x1.png, hence the link should be resolvable.
Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.
does your server respond to queries on http://172.22.2.2/, i.e. port 80 is forwarded to 8080?
No it does not. It only works when I add :8080 to the address.
Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.
This issue was closed because it is missing author input.