Make IPFS in VMs available for p2p connections from the outside #229
Labels
No Label
service
accounts
service
discourse
service
drone-ci
service
email
service
garage
service
gitea
service
ipfs
service
mastodon
service
postgres
service
remotestorage
service
wiki
service
xmpp
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/chef#229
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
go-ipfs doesn't currently know about its external IP, and thus doesn't accept requests from it. There should be some kind of config variable for this.
It can still connect to other peers itself. But e.g. people running the kredits pinner can't connect to the main gateway node now.
Status update: I worked on this for a while just now, and it appears that
Addresses.Announce
would be the correct config to use. I added some DNS-based multiaddrs to the config onipfs-1
.Instead of an error, I now get connection success announced when connecting to the draco node. However, the connection never seems to persist, as I can never see it among
ipfs swarm peers
.I have a feeling that we may need #290 for solving this properly. We can, of course, also connect our own nodes internally via the private network, too.
Update: The source of the problem described above is likely that we filter
10.0.0.0/8
addresses via config, so as not to trigger netscan reports in the data center.This has been solved recently.