now i get this error when i attempt to access it. anyone know how to set it back?

404: FetchError: request to http://lemmy:8536/api/v3/site

and the command docker compose -p lemmy-easy-deploy logs -f yeilds a bunch of nonsense but this line stood out…

Error: LemmyError { message: Some("Cannot have both private instance and federation enabled."), inner: Cannot have both private instance and federation enabled., context: "SpanTrace" }

  • Kerrigan@l.jugregator.orgEnglish
    0·
    1 year ago

    Connect to your database and execute this sql:

    UPDATE local_site SET private_instance = false

    Then restart docker container

    • Soullioness@lemmy.worldOPEnglish
      0·
      1 year ago

      Thank you for your response, but can you explain like I’m five? Lol

      I don’t know what you mean by connect to my database, I’m really new to this stuff, this is all really above my head.

      • key@lemmy.keychat.orgEnglish
        1·
        1 year ago

        To connect to your database: psql -h localhost -U PG_USER

        Replace PG_USER with the username in your docker-compose file (under the entry for postgresql). It’ll ask you for a password which will be right next to your pg user in docker compose or lemmy.hjson

        If you get an error about psql not being a valid command then you probably need to install the postgresql client tools. Depending on OS that varies, usually sudo apt install postgresql or sudo dnf install postgresql will do it.

        If you get an error about being unable to connect, you also will need to expose access to your database from docker. For that modify your docker compose file, look for something like “externalproxy” in the network section to know the name of the network you need to add to the postgresql container. You’ll see an example of it under nginx container. Put a copy of that in the postgresql docker section. You’ll also need to add port mapping 5432:5432 to PG container - again see other container entries in there for an example of the port declaration looks like. After that do docker compose up -d to reload it and you should be able to connect with psql.

        Once you get in with psql, enter that query and hit enter. It should output UPDATE 1 if it worked and then you can do \q to exit.

      • Kerrigan@l.jugregator.orgEnglish
        0·
        1 year ago

        In your case you can try this:

        $ docker exec -ti lemmy_postgresql_1 bash

        or put here your container name instead “lemmy_postgresql_1”, look inside docker ps output

        $ su postgres 
$ psql -d lemmy
$ UPDATE local_site SET private_instance = false;

        Then restart docker container with docker restart lemmy_lemmy_1 # or your container name instead “lemmy_lemmy_1”, look inside docker ps output

        • Soullioness@lemmy.worldOPEnglish
          0·
          1 year ago

          i’m so sorry but i still don’t understand…

          root@laptop:/home/rain# docker exec -ti lemmy_postgresql_1 bash
Error response from daemon: No such container: lemmy_postgresql_1

          here is the guide i followed that got me to this point… and then i checked that box with out understanding what i was doing…

          • grue@lemmy.worldEnglish
            0·
            1 year ago

            Replace lemmy_postgresql_1 with whatever the name of your database container is. If you don’t know the name, I guess you should be able to figure it out by reading config.env?

            • Soullioness@lemmy.worldOPEnglish
              2·
              1 year ago

              i don’t see the database mentioned in that file

              The hostname for your instance

              Do NOT put http:// or https://

              ONLY put your domain here. Subdomains are ok.

              LEMMY_HOSTNAME=“atosoul.zapto.org”

              If you use Cloudflare, your Cloudflare API token. Otherwise leave blank.

              If present, the DNS-01 challenge will be used to obtain valid HTTPS certificates

              –> If you use the Cloudflare Proxy, DO NOT FORGET to enable Cloudflare’s Full (Strict) SSL mode! <–

              This token must have access to edit the Zone where $LEMMY_HOSTNAME is

              Using this option will increase build time, as the DNS plugin needs to be compiled. Subsequent deploys will be faster.

              CF_API_TOKEN=“”

              Whether or not to build Lemmy from source rather than use the Docker Hub images

              This will significantly increase deploy time!

              BUILD_FROM_SOURCE=“false”

              The name of your Lemmy instance, will be displayed on the site header (only used during first-time setup)

              If you use special characters, please backslash-escape them.

              SETUP_SITE_NAME=“AtoSoul”

              ###############################################################

              SETTINGS FOR ADVANCED USERS ONLY

              I CANNOT HELP YOU WITH ISSUES RELATED TO THESE SETTINGS

              ###############################################################

              The external port to use for Caddy’s port 80

              CADDY_HTTP_PORT=80

              The external port to use for Caddy’s port 443

              CADDY_HTTPS_PORT=443

              If true/1, also deploy the postfix server and configure Lemmy to send emails

              NOTE: Port 25 is USUALLY disabled on most server providers. For this reason, the email service is not well tested

              Feedback on the email service is appreciated!

              USE_EMAIL=“false”

              If true/1, prefix the Caddy host block with http:// to disable TLS entirely

              CADDY_DISABLE_TLS=“false”

              The options below will be passed directly to lemmy.hjson

              See that file for how they will be used

              Remember to backslash escape any special characters!

              POSTGRES_POOL_SIZE=“5” TLS_ENABLED=“true” SETUP_ADMIN_USER=“lemmy” LEMMY_NOREPLY_DISPLAY=“Lemmy NoReply” LEMMY_NOREPLY_FROM=“noreply”

              • grue@lemmy.worldEnglish
                1·
                1 year ago

                Hmm… well, it must be somewhere (I don’t know much about docker). Maybe run some Docker command to list the containers, then supply the appropriate one to the grandparent commenter’s docker exec... command.