• 5 Posts
  • 38 Comments
Joined 1 year ago
Cake day: April 19th, 2023
  • Valmond@lemmy.mlOPtoLemmy Support@lemmy.ml•Help with routing SSH over nginx to lemmy-ui docker
    1·
    1 year ago

    Okay so I “found” it, but I suppose there is an underlying problem, but well it works.

    See that last commented line?

    It shuts off the default lemmy-ui at all times… It’s even in the comment! I wonder how that could ever have worked?

    So now I just have to find out if I need to forward the POST, PUT, DELETE, PATCH, CONNECT to lemmy …

    Thank you all for your patience :-)

        map "$request_method:$http_accept" $proxpass {
        # If no explicit matches exists below, send traffic to lemmy-ui
        default "http://lemmy-ui";

        # GET/HEAD requests that accepts ActivityPub or Linked Data JSON should go to lemmy.
        #
        # These requests are used by Mastodon and other fediverse instances to look up profile information,
        # discover site information and so on.
        "~^(?:GET|HEAD):.*?application\/(?:activity|ld)\+json" "http://lemmy";

        # All non-GET/HEAD requests should go to lemmy
        #
        # Rather than calling out POST, PUT, DELETE, PATCH, CONNECT and all the verbs manually
        # we simply negate the GET|HEAD pattern from above and accept all possibly $http_accept values
        #"~^(?!(GET|HEAD)).*:" "http://lemmy";
    }
  • Valmond@lemmy.mlOPtoLemmy Support@lemmy.ml•Help with routing SSH over nginx to lemmy-ui docker
    1·
    1 year ago

    More info:

    I logged in as the owner on a mobile app, and most things work okay, but upvoting another users post on my site gave an error:

    proxy_1     | 172.18.0.1 - - [20/Jul/2023:15:56:07 +0000] "POST /api/v3/post/like HTTP/1.1" 200 569 "-" "Jerboa"
proxy_1     | 172.18.0.1 - - [20/Jul/2023:15:56:07 +0000] "POST /api/v3/post/like HTTP/1.1" 200 569 "-" "Jerboa"
proxy_1     | 172.18.0.1 - - [20/Jul/2023:15:56:09 +0000] "POST /api/v3/post/like HTTP/1.1" 200 568 "-" "Jerboa"
proxy_1     | 172.18.0.1 - - [20/Jul/2023:15:56:16 +0000] "POST /api/v3/comment/like HTTP/1.1" 200 889 "-" "Jerboa"
lemmy_1     | 2023-07-20T15:56:16.441551Z  WARN lemmy_server::root_span_builder: Domains do not match
lemmy_1     |    0: lemmy_server::root_span_builder::HTTP request
lemmy_1     |            with http.method=POST http.scheme="http" http.host=lemmy.mindoki.com http.target=/inbox otel.kind="server" request_id=0b06a8ae-3676-430a-a3c7-4008e748b1e9
lemmy_1     |              at src/root_span_builder.rs:16
lemmy_1     | LemmyError { message: None, inner: Domains do not match, context: SpanTrace [{ target: "lemmy_server::root_span_builder", name: "HTTP request", fields: "http.method=POST http.scheme=\"http\" http.host=lemmy.mindoki.com http.target=/inbox otel.kind=\"server\" request_id=0b06a8ae-3676-430a-a3c7-4008e748b1e9", file: "src/root_span_builder.rs", line: 16 }] }
proxy_1     | 172.18.0.1 - - [20/Jul/2023:15:56:16 +0000] "POST /inbox HTTP/1.1" 400 20 "-" "Lemmy/0.18.2; +https://127.0.0.1"

    Does this error spread some light about what is wrong? I’m thinking especially of the https://127.0.0.1 for which I don’t have a SSL certificate (I only have one for lemmy.mindoki.com).

    I’ll try to hunt down that 127.0.07 and change it to lemmy.mindoki.com, but If you know the answer I’m all ears :-)

  • Valmond@lemmy.mltoTechnology@beehaw.org•Best Linux laptop for 2023English
    4·
    1 year ago

    That seems quite top of the line even today.

    For battery life, the screen, the screen, the GPU (seems you use an IGP), the size of the screen, and the CPU are the main culprits.

    64GB RAM will use some battery do you really need that much?

    Hopefully your 1TB is an SSD otherwise an SSD is a nice upgrade.

    There are also fat fat powerbanks for power users far away from a 110/220volt line!

    I Am curious, most often power hungry laptops are gaming ones… What do you do with yours?

  • Valmond@lemmy.mlOPtoLemmy Support@lemmy.ml•Simple nginx configEnglish
    1·
    1 year ago

    EDIT: The site itself works now, so I “only” need help with nginx :-)

    EDIT: DISCARD THE FOLLOWING LINES (Strike-through doesn’t seem to work):

    ~~BTW, I get a handful of errors when I start Lemmy :

    thread ‘main’ panicked at 'Error connecting to postgres://lemmy:thepassword@postgres:5432/lemmy: could not connect to server: Connection refused

    lemmy_1 | Is the server running on host “postgres” (172.18.0.2) and accepting

    lemmy_1 | TCP/IP connections on port 5432?

    I do not know at all where that 172.18.0.2 address comes from sweating :-D~~

  • Valmond@lemmy.mlOPtoLemmy Support@lemmy.ml•Simple nginx configEnglish
    1·
    1 year ago

    Hello, I’m back with more questions and clarifications!

    This is what I did to install Lemmy:

    Install a fresh Linux Mint on an old PC.

    Follow the ‘official’ docker install: https://join-lemmy.org/docs/administration/install_docker.html

    I continued with nginx, lets encrypt etc.

    I also installed PosgreSQL and added a user Lemmy.

    I forward a TCP connection from my fix public IP to the lemmy PC and pointed lemmy.mindoki.com with an A redirection onto that public IP:PORT.

    The only ‘exotic’ thing done was that I added these lines to /home/fediverse/.bashrc :

    export LEMMY_CONFIG_LOCATION=“/media/fediverse/Storage/lemmy/lemmy.hjson”

    EMMY_DATABASE_URL=“postgres://lemmy:redacted_password@localhost:5432/lemmy”

    . “$HOME/.cargo/env”

    I don’t think (but not completely sure) that the last line was added by me manually.

    Now I can access Lemmy locally on localhost:1236 and everything works (inscription, creations of ‘subs’ etc).

    I added the nginx.conf config file at the end of this message (some lines are commented out to make it work at all).

    Almost feels like I should have a very much shorter nginx config file 🙃

    Thanks again!

    Cheers

    EDIT: I messed something up, the server now only answers “Server error”, I’ll be back later …