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

Open ports check fail due to a bug in ncp-diag file #1486

Closed
Soiuke opened this issue Jun 5, 2022 · 7 comments
Closed

Open ports check fail due to a bug in ncp-diag file #1486

Soiuke opened this issue Jun 5, 2022 · 7 comments

Comments

@Soiuke
Copy link

Soiuke commented Jun 5, 2022

ncp-diag file

Line 79

Add "/check" after "https://portchecker.co"

Otherwise port check 80 and 443 anwser "closed" erroneously (even when these ports are correctly opened and working)

Congratulations for you exelent work and thanks to you and all ncp comunity.

@dd900
Copy link

dd900 commented Jun 19, 2022

Can confirm making this edit fixes the issue of NextCloudPi Panel showing ports closed even though they were open.

@schoetju
Copy link
Contributor

Can confirm the bugfix too.
@Soiuke Do you mind to create a fork plus a corresponding pull-request?

BTW: This issue is the same as #1475 , isn't it?

@Oberlurch3000
Copy link

I can also confirm that solved the issue for me. Btw: No spacebar between "https://portchecker.co" and "/check" => "https://portchecker.co/check"

@theCalcaholic
Copy link
Collaborator

Thank you for the additional info!

I'm going to close this issue though, because it's a duplicate of #1475

@spiritualcrab
Copy link

ncp-diag file

Line 79

Add "/check" after "https://portchecker.co"

Otherwise port check 80 and 443 anwser "closed" erroneously (even when these ports are correctly opened and working)

Congratulations for you exelent work and thanks to you and all ncp comunity.

I am sorry, but how to find this file in order to edit it?

@LittleAlf
Copy link

/usr/local/bin/ncp-diag

@Soiuke
Copy link
Author

Soiuke commented Jul 27, 2022

Can confirm the bugfix too. @Soiuke Do you mind to create a fork plus a corresponding pull-request?

BTW: This issue is the same as #1475 , isn't it?

@schoetju I've not created a fork and pull-request because I think that this is a "minor" issue, which does not affect the main functionality of the project. As far as @theCalcaholic knows about the issue and also the proposed solution, I think that he can modify ncp-diag file in the main project/branch.

Otherwise please tell me if I must open a fork and pull-request in order to incorporate the solution to the main project.

By the other hand, I apologize for duplicating issues.

Thanks to all the ncp community. Congratulations to @nachoparker for his great work during last years, and thanks to @theCalcaholic for leading the project from now on.

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

7 participants