Configuration de Discourse : suppose que nc est installé

Contribuer Bug
1

Ran through the install using discourse-setup (I don’t think I ever have yet, so no time like the present!) and the following error showed up:

Checking your domain name . . .
WARNING:: This server does not appear to be accessible at dotest.example.net:443.

A connection to http://dotest.example.net (port 80) also fails.

This suggests that dotest.example.net resolves to the wrong IP address
or that traffic is not being routed to your server.

Google: "open ports YOUR CLOUD SERVICE" for information for resolving this problem.

You should probably answer "n" at the next prompt and disable Let's Encrypt.

This test might not work for all situations,
so if you can access Discourse at http://dotest.example.net, you might try anyway.

I believe this happened as nc isn’t installed so it couldn’t properly run the test. We should ensure nc is available before erroring out on this check.

3 « J'aime »
2

I totally believe that I assumed that nc was installed and that on some OSs it’s not.

The messages do suggest that it could be wrong. Did Let’s Encrypt work?

What OS is this? What cloud service?

2 « J'aime »
3

Fresh debian-9 on DO.

Everything else worked A-OK and it’s up and running great! :+1:

3 « J'aime »
4

Hmm. Then the question becomes, does discourse-doctor install nc just for one test that might not be necessary, or just say, “well, you don’t have nc, so you’re on your own to see that you have ports open and mapped correctly.”?

I don’t like installing software if it’s not necessary. I think I’ll change the message to recommend installing nc if they want it.

@codinghorror? @mpalmer want to weigh in?

5

Wasn’t this addressed in a different way by @supermathie?

6

I’m all for this :+1:

I addressed the problem where Discourse’s email test rake task didn’t properly pick up the STARTTLS option. This is separate.

2 « J'aime »
7

In that case either stop the script and tell them to re-run with nc installed, or print a warning that the check was skipped because nc was not installed?

2 « J'aime »
8

I was going to let the script continue with the warning, adding the bit about nc. As it is, it does work, it just suggests that it probably won’t.

4 « J'aime »
9

Peut-on clore ce ticket comme étant résolu @pfaffman ?

10

Eh bien, six mois se sont écoulés. Je n’ai pas ajouté de message du type « vous n’avez pas nc, donc je ne peux pas tester vos ports », mais personne ne s’est plaint. Peut-être que le libellé :

     Google : "ports ouverts VOTRE SERVICE CLOUD" pour obtenir des informations afin de résoudre ce problème.
    
     Vous devriez probablement répondre "n" à l'invite suivante et désactiver Let's Encrypt.
    
     Ce test pourrait ne pas fonctionner dans toutes les situations,
     donc si vous pouvez accéder à Discourse via http://$HOST, vous pouvez essayer quand même.

est suffisant. Ce n’était jamais un :bug:, mais plutôt une gêne pour quelqu’un qui avait assez de bon sens en administration système pour ne pas vouloir utiliser Ubuntu. Cela fonctionne comme prévu sur Ubuntu (je n’ai pas vérifié les autres distributions). Je suis enclin à laisser dormir ce chien.

5 « J'aime »