Zelf-gehoste discourse-instantie voegt "7d" toe aan de FQDN

Fout
,
1

Hello everyone,

I am new to Discourse self-hosting. I am installing this on a server that’s running other web services. So I have my own Nginx, which will proxy connections to the Discourse container. I also have a full-fledged SMTP server to handle the emails.

I have two questions.

  1. Following the documentation to install Discourse, it pulled the development version ( 3.5.0.beta7-dev). I don’t want to run this version. How do I make it pull the latest release version instead?

  2. While testing the email delivery, I realized that clicking on that link leads to a distorted URL for the site. My site runs on a FQDN that is discourse.my.domain. However, when I click on the link to test the email, it leads to http://community.kictanet.or.ke7d/admin/email/server-settings - there is a “7d” appended to the end of the FQDN. If I remove the “7d”, the URL loads fine. Where is the “7d” coming from, and how do I ensure it doesn’t happen?

Thank you.

2 likes
2

That is the latest version :slightly_smiling_face: . It’s on the beta branch.
For more info about branches, see:

1 like
3

Hartelijk dank voor de snelle reactie.
Ik heb mijn containers/app.yml bekeken en de versie regel niet ontcomment:

## Welke Git-revisie moet deze container gebruiken? (standaard: tests-passed)
  #version: tests-passed

Moet ik er daarom tevreden mee zijn dat de geïnstalleerde versie goed genoeg is voor productiegebruik?

4

Ja, dat is het. Dit forum (Discourse Meta) gebruikt ook die versie. De standaard en aanbevolen versie is om de tests-passed branch te gebruiken.

1 like
5

Hartelijk dank.

Heeft u enig inzicht in waar die “7d” wordt toegevoegd aan de FDQN?

6

Nee, sorry. Ik heb geen idee waarom dat gebeurt. Heeft u toevallig een CDN of reverse proxy?

7

I don’t have a CDN. However, I run my Discourse instance behind Nginx with a very simple config:

server {
        listen 443 ssl http2;
        server_name discourse.FQDN;

        # SSL parameters
        ssl_certificate /etc/letsencrypt/live/discourse.FQDN/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/discourse.FQDN/privkey.pem;
        ssl_trusted_certificate /etc/letsencrypt/live/discourse.FQDN/chain.pem;
        include snippets/ssl.conf;
        include snippets/letsencrypt.conf;


        # Tell browsers the site should only be accessed via https.
        add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
        add_header Content-Security-Policy upgrade-insecure-requests;

        # log files
        access_log /var/log/nginx/discourse.FQDN-access.log;
        error_log /var/log/nginx/discourse.FQDN-error.log;


        location = /favicon.ico {
        log_not_found off;
        access_log off;
        }

        location = /robots.txt {
        allow all;
        log_not_found off;
        access_log off;
        }

        client_max_body_size 10m;
        proxy_read_timeout 300;

        location / {
        proxy_pass http://127.0.0.1:8008;
        proxy_http_version  1.1;
        proxy_cache_bypass  $http_upgrade;
        proxy_set_header Host              $host;
        proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
        proxy_set_header X-Real-IP         $remote_addr;
        proxy_set_header X-Forwarded-Host  $host;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Port  $server_port;
        }

        location @rewrites {
                add_header X-Cache-Engine "No cache";
                rewrite ^ /index.php last;
        }

}
1 like
8

This looks like a mistake in the admin quick start guide:

I’ve submitted a fix here:

If you want, you could edit the topic and fix the link in the topic on your forum. Or you can wait for the pull request to be merged, then update your forum and reseed that topic at the admin > site texts page using the “replace text …” button on the right.

5 likes
9

Thank you for finding the source of the problem.
I am only on my 2nd day with the Discourse installation so I am even yet to figure out how to find a topic and edit it :slight_smile:
A lof of reading yet to be done towards running/administering own self-hosted instance.

1 like
10

Thank you for bringing this to my attention. Welcome to Meta :wave:

You can edit it using the pencil in the post menu:


The guide should be in your staff category. Maybe you also have the “Getting Started” link at the top next to the logo. I think that one takes you to the topic too.

2 likes
11

Bedankt. Ik ben begonnen via de link "Aan de slag" en heb het bewerkt.

1 like
12

thank you for the report @odhiambo, and welcome to Discourse Meta - great first post :smiley:
Good luck with your new forum!

thanks for the fix Moin. the doc is updated now :slight_smile:

1 like
13

Ik weet niet precies waar het vandaan komt. Maar het verdween vanzelf bij mij. Ik heb al mijn instellingen in mijn emv yaml uitgecommentarieerd, ik weet niet of dat er iets mee te maken heeft. Maar dat heeft een andere fout voor mij opgelost

14

I think I know where it’s coming from. :raised_hand: :slight_smile:

2 likes
15

Dat zou het wel doen lollll.

16

Sudden irony just filled me, were chatting on a forum about fixing said forum :rofl:

17

@ryan_olsen From /about :wink:

About

A place for the Discourse community to meet, ask questions, provide support to one other, and share much-appreciated feedback.

Hi @odhiambo , you can read the guides in Documentation > Using Discourse and Documentation > Site Management. They’re really helpful to learn more about Discourse’s features!

1 like
18

Dit onderwerp is automatisch gesloten na 23 uur. Nieuwe reacties zijn niet meer toegestaan.