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.

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

Conjure PT receives invalid phantom IPs from the station #285

Open
onyiny-ang opened this issue Jan 8, 2025 · 3 comments
Open

Conjure PT receives invalid phantom IPs from the station #285

onyiny-ang opened this issue Jan 8, 2025 · 3 comments
Assignees

Comments

@onyiny-ang
Copy link

Conjure connections seem to be failing for the Tor PT which we have documented in this issue.
The client receives the IP 0.0.0.0 from the conjure station and fails to connect.
Is it possible something changed in #282 (or since) that might be behind this?

@onyiny-ang onyiny-ang changed the title Conjure receives invalid phantom IPs from the station Conjure PT receives invalid phantom IPs from the station Jan 8, 2025
@0x90-n 0x90-n self-assigned this Jan 8, 2025
@0x90-n
Copy link
Contributor

0x90-n commented Jan 8, 2025

Hey @onyiny-ang, thanks for taking the time to file this issue.
Would the issue still persist if you set the -registrar to bdapi and the -api-endpoint to https://registration.refraction.network/api/register-bidirectional?
This could be an issue with gotapdance not validating options properly. In fact, I was able to reproduce the same issue (the IP the client receives is 0.0.0.0, and refused connection) when I set conflicting options when running gotapdance cli e.g. set -registrar to bdapi and -api-endpoint to https://registration.refraction.network/api/register (instead of https://registration.refraction.network/api/register-bidirectional).

@onyiny-ang
Copy link
Author

We are already using the register-bidirectional endpoint so I don't think this is the issue, unless I'm missing something.

@cohosh
Copy link
Contributor

cohosh commented Jan 28, 2025

Looks like this was just a domain fronting configuration issue with Tor's CDN configuration. It can be closed :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants