Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bind multiple addresses/interfaces to API and Gateway #1649

Closed
BrendanBenshoof opened this issue Sep 4, 2015 · 3 comments
Closed

Bind multiple addresses/interfaces to API and Gateway #1649

BrendanBenshoof opened this issue Sep 4, 2015 · 3 comments
Labels
kind/enhancement A net-new feature or improvement to an existing feature

Comments

@BrendanBenshoof
Copy link

Currently I cannot bind the gateway and api to multiple addresses and I am forced to use ipv4/0.0.0.0 OR ipv6/:: which means I can only bind them to one protocol or the other.

Suggested fix:
Allow a list of bind addresses for both API and Gateway
@jbenet
Copy link
Member

jbenet commented Sep 5, 2015

👍 to making these lists. need to:

  • add support for list
  • add to a migration (dev0.4.0 or later, i say)

@em-ly em-ly added the kind/enhancement A net-new feature or improvement to an existing feature label Aug 25, 2016
@Mikaela
Copy link
Contributor

Mikaela commented Apr 1, 2019 •
edited
Loading

This has been fixed or at least I have my gateway and API on both 127.0.0.1 and ::1.

Edit: I think #5905 is related.

@Stebalien
Copy link
Member

Yes, this has been fixed. The remaining issue is binding on both by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement A net-new feature or improvement to an existing feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@jbenet @Stebalien @Mikaela @BrendanBenshoof @em-ly