-
Notifications
You must be signed in to change notification settings - Fork 986
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.
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
Communicate with bootnodes, mailservers and whisper nodes by :443 (staging, test, beta) #7382
Conversation
Jenkins BuildsClick to see older builds (15)
|
I tried it locally in iOS simulator where Little Snitch blocked all Status trafic except :80 and :443 and it seems to help. On |
@jakubgs it looks like we can proceed and setup the same stuff on This PR changes a few of them for |
Ah yeah, because I was updating keys in Consul by hand, I must have missed one or two, my bad. I'll make sure to not do that on Beta. |
@jakubgs so, ping me when you will do that and then I will be able to update and un-WIP this PR. |
Pull Request Checklist
|
Latest builds here for Android, iOS, MacOS builds were tested. From @mandrigin do we intentionally keep mail-03.do-ams3.eth.beta, mail-03.do-ams3.eth.beta, mail-03.do-ams3.eth.beta staying to use 30504 port? If yes, then it ready for merge |
@Serhy yeah, I just followed whatever is in http://fleets.status.im |
I don't see |
16fcb55
to
f21e378
Compare
fixed that |
@Serhy can we re-run e2e tests on this branch when the build is complete? I fixed the last ports, so if e2e pass, I think it is safe to merge. |
@mandrigin, @jakubgs thanks for update. |
@Serhy android-e2e is done, so we can run tests now. |
e2e tests are in progress now... |
100% of end-end tests have passed
Passed tests (58)Click to expand
|
@mandrigin for me |
@Serhy what is your IP or peer ID? You might be a stale peer on that mailserver. |
@jakubgs My IP: 213.160.136.62 |
Hmmm, I don't see you in peers on But I checked on the host and it was missing the firewall rule: [email protected]:~ % sudo iptables -t nat -L PREROUTING
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
DOCKER all -- anywhere anywhere ADDRTYPE match dst-type LOCAL And I saw that the healtcheck was failing: [email protected]:~ % sudo iptables -t nat -L PREROUTING
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
DOCKER all -- anywhere anywhere ADDRTYPE match dst-type LOCAL
REDIRECT tcp -- anywhere anywhere tcp dpt:https /* Redirect 443 to 30504 */ redir ports 30504 Thanks for reporting this. |
Yeah, at that time I was on this PR build, and failing to establish the connection with mail-01. iOS builds failing to succeed, @jakubgs could you take a look please? |
Yeah, no idea what that's about. Xcode fails to build but there is no error whatsoever. |
@Serhy now it passes. I've no idea what was it... |
Cool! Mailservers are OK with iOS build too. |
…aging, test) Signed-off-by: Igor Mandrigin <[email protected]>
f21e378
to
2c77822
Compare
fixes #6645
fixes #6351
Summary:
Essentially, we use HTTPS port :443 to connect to our nodes.
TODO:
eth.beta
too.Areas that maybe impacted (optional)
Functional
NB! "test" or "staging" fleet should be used to test it.
Steps to test:
status: ready