إعداد Discourse: يفترض أن nc مثبت

ساهم خلل
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 إعجابات
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)
3

Fresh debian-9 on DO.

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

3 إعجابات
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)
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)
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 إعجابات
9

هل يمكننا إغلاق هذا باعتباره جيدًا @pfaffman؟

10

حسناً، لقد مرّ 6 أشهر. لم أقم بإضافة رسالة تقول “لا تملك nc، لذا لا يمكنني اختبار منافذك”، لكن لم يشكّ أحد آخر. ربما تكون الصياغة التالية كافية:

     Google: \"open ports YOUR CLOUD SERVICE\" للحصول على معلومات لحل هذه المشكلة.
    
     يُرجى الإجابة بـ \"n\" في المطالبة التالية وتعطيل Let's Encrypt.
    
     قد لا تعمل هذه الاختبارات في جميع الحالات،
     لذا إذا كان بإمكانك الوصول إلى Discourse عبر http://$HOST، فربما تحاول الأمر على أي حال.

لم يكن الأمر :bug: أبداً، بل مجرد إزعاج لشخص لديه ما يكفي من الخبرة الإدارية للنظم ليُفضّل عدم استخدام Ubuntu. يعمل كما هو متوقع على Ubuntu (لم أتحقق من التوزيعات الأخرى). أميل إلى ترك هذا الأمر كما هو دون تدخل.

5 إعجابات