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

FAQ: timeout on port 443 is not acceptable. #360

Closed
leamas opened this issue Sep 27, 2010 · 4 comments
Closed

FAQ: timeout on port 443 is not acceptable. #360

leamas opened this issue Sep 27, 2010 · 4 comments

Comments

@leamas
Copy link

leamas commented Sep 27, 2010

According to the FAQ, port 443 on the server housing diaspora must block, not just timeout on connection attempts. For me, it has been hard to achieve this - I get a timeout from my router in whatever setup I've tried.

Basically, this makes it hard for me to run diaspora. Part of problem is that I have no idea in what way this is supposed to affect the application, and this thus becomes a possible source of all kinds of issues.
@koo5
Copy link

koo5 commented Sep 27, 2010

its a problem when someone from another server tries to add you. Im dont know if the bug is still there. Forward it to your computer and close it on it with a firewall (i use guarddog on ubuntu) is a solution.

@leamas
Copy link
Author

leamas commented Sep 28, 2010

I have exactly this problem adding myself from a remote server. Unfortunately, I've been unable to block the port - it seems like my router tries to do something clever with port 443 causing timeout even if the port is blocked (works fine w other ports).

Basically, I think that this bug is still there. For me, it's a partially blocking error disabling access to my server. from remote peers.

@leamas
Copy link
Author

leamas commented Sep 30, 2010

Um... using tcp-reset seems to make the trick.. See http://github.com/diaspora/diaspora/wiki/Handling-bug-360.

@rsofaer
Copy link
Member

rsofaer commented Oct 8, 2010

This problem is centered on the limitations of the Redfinger gem. Redfinger doesn't react well to a timeout when it tries to retrieve a webfinger profile over HTTPS. Hopefully we'll move off of it soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@koo5 @rsofaer @leamas @diaspora-redmine-github-migration