Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Postiz
  3. Impossible to log in any SM account on Postiz

Impossible to log in any SM account on Postiz

Scheduled Pinned Locked Moved Postiz
13 Posts 6 Posters 646 Views 6 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • perelinP Offline
    perelinP Offline
    perelin
    wrote on last edited by
    #2

    Same issue with Instagram. Credentials are set in the .env file as descibed in the docs.
    image.png

    1 Reply Last reply
    1
    • BrutalBirdieB Offline
      BrutalBirdieB Offline
      BrutalBirdie
      Partner
      wrote on last edited by
      #3

      @Dont-Worry // @perelin will try to reproduce this in the evening (CEST Timetzone) and see if I can find a fix.

      Like my work? Consider donating a drink. Cheers!

      1 Reply Last reply
      2
      • perelinP Offline
        perelinP Offline
        perelin
        wrote on last edited by
        #4

        @BrutalBirdie thanks for the effort. Please tell if you need some debuging infos from our side.

        1 Reply Last reply
        1
        • robiR Offline
          robiR Offline
          robi
          wrote on last edited by
          #5

          Perhaps this was a way for the developer to gain enough interest and contributors by adding a bunch of unfinished and broken services.

          Conscious tech

          1 Reply Last reply
          2
          • D Dont-Worry

            Hello,

            After I created an app on linkedIn, and added in the .env the :
            LINKEDIN_CLIENT_ID="XXXX"
            LINKEDIN_CLIENT_SECRET="XXXX"

            I restarted the app multiple times and still got the same error. Idk what to do..

            7a1ff0c3-b439-44d2-836f-89204c5a622a-image.png

            BrutalBirdieB Offline
            BrutalBirdieB Offline
            BrutalBirdie
            Partner
            wrote on last edited by
            #6

            @Dont-Worry
            Did you really follow all these steps? https://docs.postiz.com/providers/linkedin

            Want to make sure before I do them 😄

            Like my work? Consider donating a drink. Cheers!

            1 Reply Last reply
            1
            • perelinP Offline
              perelinP Offline
              perelin
              wrote on last edited by
              #7

              For our side I can say that we followed all steps at https://docs.postiz.com/providers/instagram and put the resulting credentials in the env.sh file and reloaded the app. When we want to add Instagram as a channel we are linked out to an error page on meta/facebook that says "App ID invalid"
              Screenshot 2025-04-24 at 09.31.53.png

              Looking at the linkout URL it seems the client_id is not set.

              Screenshot 2025-04-24 at 09.34.50.png

              If I set the client_id parameter manually to our FACEBOOK_APP_ID from env.sh the authorisation process starts. At first it looks to go through, but after redirecting to Postiz I get this error:

              bdc2be85-3a2a-4bce-81ff-4a53681d4694-image.png

              Log file at this time:

              Apr 24 09:36:34 13:M 24 Apr 2025 07:36:34.012 * 10 changes in 300 seconds. Saving...
              Apr 24 09:36:34 13:M 24 Apr 2025 07:36:34.013 * Background saving started by pid 3078
              Apr 24 09:36:34 13:M 24 Apr 2025 07:36:34.114 * Background saving terminated with success
              Apr 24 09:36:34 3078:C 24 Apr 2025 07:36:34.020 * DB saved on disk
              Apr 24 09:36:34 3078:C 24 Apr 2025 07:36:34.021 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
              Apr 24 09:38:29 2025-04-24T07:38:29Z
              Apr 24 09:38:29 2025-04-24T07:38:29Z
              Apr 24 09:38:29 [Nest] 130 - 04/24/2025, 7:38:29 AM WARN OpenAI API key not set, chat functionality will not work
              Apr 24 09:38:29 Node.js v20.18.2
              Apr 24 09:38:29 UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "#<RefreshToken>".
              Apr 24 09:38:29 ^
              Apr 24 09:38:29 at process.processTicksAndRejections (node:internal/process/task_queues:96:32) {
              Apr 24 09:38:29 at processPromiseRejections (node:internal/process/promises:470:17)
              Apr 24 09:38:29 at throwUnhandledRejectionsMode (node:internal/process/promises:389:7)
              Apr 24 09:38:29 code: 'ERR_UNHANDLED_REJECTION'
              Apr 24 09:38:29 new UnhandledPromiseRejection(reason);
              Apr 24 09:38:29 node:internal/process/promises:389
              Apr 24 09:38:29 {"error":{"message":"Missing or invalid client id.","type":"OAuthException","code":101,"fbtrace_id":"AQjOzXIs8yqUOOGZn6sXIys"}}
              Apr 24 09:38:29 }
              Apr 24 09:38:30 TypeError: fetch failed
              Apr 24 09:38:30 [cause]: SocketError: other side closed
              Apr 24 09:38:30 at Socket.<anonymous> (node:internal/deps/undici/undici:6294:28)
              Apr 24 09:38:30 at Socket.emit (node:events:530:35)
              Apr 24 09:38:30 at async /app/code/dist/apps/frontend/.next/server/app/(site)/integrations/social/[provider]/continue/page.js:3:28297
              Apr 24 09:38:30 at async ic (/app/code/dist/apps/frontend/.next/server/app/(site)/integrations/social/[provider]/continue/page.js:3:26983) {
              Apr 24 09:38:30 at endReadableNT (node:internal/streams/readable:1698:12)
              Apr 24 09:38:30 at node:internal/deps/undici/undici:13502:13
              Apr 24 09:38:30 at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
              Apr 24 09:38:30 bytesRead: 0
              Apr 24 09:38:30 bytesWritten: 1844,
              Apr 24 09:38:30 code: 'UND_ERR_SOCKET',
              Apr 24 09:38:30 digest: '1372167340',
              Apr 24 09:38:30 localAddress: '::1',
              Apr 24 09:38:30 localPort: 55620,
              Apr 24 09:38:30 npm notice
              Apr 24 09:38:30 npm notice
              Apr 24 09:38:30 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.3.0
              Apr 24 09:38:30 npm notice New major version of npm available! 10.8.2 -> 11.3.0
              Apr 24 09:38:30 npm notice To update run: npm install -g npm@11.3.0
              Apr 24 09:38:30 remoteAddress: '::1',
              Apr 24 09:38:30 remoteFamily: 'IPv6',
              Apr 24 09:38:30 remotePort: 3000,
              Apr 24 09:38:30 socket: {
              Apr 24 09:38:30 timeout: undefined,
              Apr 24 09:38:30 {"level":"error","ts":1745480310.3278437,"logger":"http.log.error","msg":"EOF","request":{"remote_ip":"172.18.0.1","remote_port":"35770","client_ip":"172.18.0.1","proto":"HTTP/1.1","method":"POST","host":"postiz.claudron.OURSERVER.de","uri":"/api/copilot/chat","headers":{"Origin":["https://postiz.claudron.OURSERVER.de"],"X-Forwarded-Host":["postiz.claudron.OURSERVER.de"],"X-Forwarded-Port":["443"],"Accept-Encoding":["gzip, deflate, br, zstd"],"Sec-Fetch-Mode":["cors"],"Priority":["u=1, i"],"User-Agent":["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36"],"Sec-Ch-Ua-Platform":["\"macOS\""],"Accept":["application/graphql-response+json, application/graphql+json, application/json, text/event-stream, multipart/mixed"],"X-Forwarded-Proto":["https"],"Sec-Fetch-Site":["same-origin"],"Sec-Fetch-Dest":["empty"],"X-Real-Ip":["46.223.213.127"],"Connection":["close"],"Referer":["https://postiz.claudron.OURSERVER.de/integrations/social/instagram?code=AQBnG8A4zYRd27Sa7_7BS78Igi0DyhPcl3jdoC75v7nu9SXxTlRoih2h3SwYMXLe0RY2IShhTSyfrEWsdYPimvWBdacLR-fGJy1Pwz3nHj8DsxPnrgJT-2ymi0oXZy-gxkfBc5Fqiw9hGD3OnXWnFwnw-3QwFeWDLm3-uu5uoro2tO9PxQPPFftrCpHlwz26p86UiNkkJWrDY2VE9b04esMKejCKrWRtU7R8yBt3gz4tcGr1V97KFQASK-K7bsKBuSaIJZi8mpc-aiWLSBhvHc5pUux4g7gqKSGeM9kbvFnFy3F1PH7nxKWQLeIlARyRvGbi4-3nEPm8Rfw_ABah-GdN21sO-mWp3iqfhcSlHiHT0PwAVYhUHnZ59J-X_B9Zr41j0L3lbiDfVFdJqag0OOR_a9oWDKc7XCzT0FIAOCGvdg&state=zlLtoo"],"Sec-Ch-Ua":["\"Chromium\";v=\"135\", \"Not-A.Brand\";v=\"8\""],"Dnt":["1"],"X-Copilotkit-Runtime-Client-Gql-Version":["1.8.5"],"X-Forwarded-For":["46.223.213.127"],"X-Forwarded-Ssl":["on"],"Content-Length":["209"],"Cookie":["REDACTED"],"Accept-Language":["en-GB,en-US;q=0.9,en;q=0.8"],"Content-Type":["application/json"],"Sec-Ch-Ua-Mobile":["?0"]}},"duration":0.829163942,"status":502,"err_id":"nxr9zs32h","err_trace":"reverseproxy.statusError (reverseproxy.go:1373)"}
              Apr 24 09:38:30 }
              Apr 24 09:38:30 }
              Apr 24 09:38:30 }
              Apr 24 09:38:31 2025-04-24 07:38:31,012 WARN exited: backend (exit status 1; not expected)
              Apr 24 09:38:32 2025-04-24 07:38:32,146 INFO spawned: 'backend' with pid 192
              Apr 24 09:38:33 2025-04-24T07:38:33Z
              Apr 24 09:38:33 2025-04-24T07:38:33Z
              Apr 24 09:38:33 2025-04-24 07:38:33,120 INFO success: backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
              Apr 24 09:38:33 > gitroom@0.0.0 start:prod
              Apr 24 09:38:33 > node dist/apps/backend/main.js
              

              After Postiz has restarted and I retry the redirect URL I get this error:

              51ab1d37-2516-4f45-8d64-6c08fddb62aa-image.png

              This is the redirect URL:

              https://postiz.claudron.OURSERVER.de/integrations/social/instagram?code=AQDvNogLUgbQ-BA....

              Not sure what to try next.

              BrutalBirdieB 1 Reply Last reply
              3
              • perelinP perelin

                For our side I can say that we followed all steps at https://docs.postiz.com/providers/instagram and put the resulting credentials in the env.sh file and reloaded the app. When we want to add Instagram as a channel we are linked out to an error page on meta/facebook that says "App ID invalid"
                Screenshot 2025-04-24 at 09.31.53.png

                Looking at the linkout URL it seems the client_id is not set.

                Screenshot 2025-04-24 at 09.34.50.png

                If I set the client_id parameter manually to our FACEBOOK_APP_ID from env.sh the authorisation process starts. At first it looks to go through, but after redirecting to Postiz I get this error:

                bdc2be85-3a2a-4bce-81ff-4a53681d4694-image.png

                Log file at this time:

                Apr 24 09:36:34 13:M 24 Apr 2025 07:36:34.012 * 10 changes in 300 seconds. Saving...
                Apr 24 09:36:34 13:M 24 Apr 2025 07:36:34.013 * Background saving started by pid 3078
                Apr 24 09:36:34 13:M 24 Apr 2025 07:36:34.114 * Background saving terminated with success
                Apr 24 09:36:34 3078:C 24 Apr 2025 07:36:34.020 * DB saved on disk
                Apr 24 09:36:34 3078:C 24 Apr 2025 07:36:34.021 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
                Apr 24 09:38:29 2025-04-24T07:38:29Z
                Apr 24 09:38:29 2025-04-24T07:38:29Z
                Apr 24 09:38:29 [Nest] 130 - 04/24/2025, 7:38:29 AM WARN OpenAI API key not set, chat functionality will not work
                Apr 24 09:38:29 Node.js v20.18.2
                Apr 24 09:38:29 UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "#<RefreshToken>".
                Apr 24 09:38:29 ^
                Apr 24 09:38:29 at process.processTicksAndRejections (node:internal/process/task_queues:96:32) {
                Apr 24 09:38:29 at processPromiseRejections (node:internal/process/promises:470:17)
                Apr 24 09:38:29 at throwUnhandledRejectionsMode (node:internal/process/promises:389:7)
                Apr 24 09:38:29 code: 'ERR_UNHANDLED_REJECTION'
                Apr 24 09:38:29 new UnhandledPromiseRejection(reason);
                Apr 24 09:38:29 node:internal/process/promises:389
                Apr 24 09:38:29 {"error":{"message":"Missing or invalid client id.","type":"OAuthException","code":101,"fbtrace_id":"AQjOzXIs8yqUOOGZn6sXIys"}}
                Apr 24 09:38:29 }
                Apr 24 09:38:30 TypeError: fetch failed
                Apr 24 09:38:30 [cause]: SocketError: other side closed
                Apr 24 09:38:30 at Socket.<anonymous> (node:internal/deps/undici/undici:6294:28)
                Apr 24 09:38:30 at Socket.emit (node:events:530:35)
                Apr 24 09:38:30 at async /app/code/dist/apps/frontend/.next/server/app/(site)/integrations/social/[provider]/continue/page.js:3:28297
                Apr 24 09:38:30 at async ic (/app/code/dist/apps/frontend/.next/server/app/(site)/integrations/social/[provider]/continue/page.js:3:26983) {
                Apr 24 09:38:30 at endReadableNT (node:internal/streams/readable:1698:12)
                Apr 24 09:38:30 at node:internal/deps/undici/undici:13502:13
                Apr 24 09:38:30 at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
                Apr 24 09:38:30 bytesRead: 0
                Apr 24 09:38:30 bytesWritten: 1844,
                Apr 24 09:38:30 code: 'UND_ERR_SOCKET',
                Apr 24 09:38:30 digest: '1372167340',
                Apr 24 09:38:30 localAddress: '::1',
                Apr 24 09:38:30 localPort: 55620,
                Apr 24 09:38:30 npm notice
                Apr 24 09:38:30 npm notice
                Apr 24 09:38:30 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.3.0
                Apr 24 09:38:30 npm notice New major version of npm available! 10.8.2 -> 11.3.0
                Apr 24 09:38:30 npm notice To update run: npm install -g npm@11.3.0
                Apr 24 09:38:30 remoteAddress: '::1',
                Apr 24 09:38:30 remoteFamily: 'IPv6',
                Apr 24 09:38:30 remotePort: 3000,
                Apr 24 09:38:30 socket: {
                Apr 24 09:38:30 timeout: undefined,
                Apr 24 09:38:30 {"level":"error","ts":1745480310.3278437,"logger":"http.log.error","msg":"EOF","request":{"remote_ip":"172.18.0.1","remote_port":"35770","client_ip":"172.18.0.1","proto":"HTTP/1.1","method":"POST","host":"postiz.claudron.OURSERVER.de","uri":"/api/copilot/chat","headers":{"Origin":["https://postiz.claudron.OURSERVER.de"],"X-Forwarded-Host":["postiz.claudron.OURSERVER.de"],"X-Forwarded-Port":["443"],"Accept-Encoding":["gzip, deflate, br, zstd"],"Sec-Fetch-Mode":["cors"],"Priority":["u=1, i"],"User-Agent":["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36"],"Sec-Ch-Ua-Platform":["\"macOS\""],"Accept":["application/graphql-response+json, application/graphql+json, application/json, text/event-stream, multipart/mixed"],"X-Forwarded-Proto":["https"],"Sec-Fetch-Site":["same-origin"],"Sec-Fetch-Dest":["empty"],"X-Real-Ip":["46.223.213.127"],"Connection":["close"],"Referer":["https://postiz.claudron.OURSERVER.de/integrations/social/instagram?code=AQBnG8A4zYRd27Sa7_7BS78Igi0DyhPcl3jdoC75v7nu9SXxTlRoih2h3SwYMXLe0RY2IShhTSyfrEWsdYPimvWBdacLR-fGJy1Pwz3nHj8DsxPnrgJT-2ymi0oXZy-gxkfBc5Fqiw9hGD3OnXWnFwnw-3QwFeWDLm3-uu5uoro2tO9PxQPPFftrCpHlwz26p86UiNkkJWrDY2VE9b04esMKejCKrWRtU7R8yBt3gz4tcGr1V97KFQASK-K7bsKBuSaIJZi8mpc-aiWLSBhvHc5pUux4g7gqKSGeM9kbvFnFy3F1PH7nxKWQLeIlARyRvGbi4-3nEPm8Rfw_ABah-GdN21sO-mWp3iqfhcSlHiHT0PwAVYhUHnZ59J-X_B9Zr41j0L3lbiDfVFdJqag0OOR_a9oWDKc7XCzT0FIAOCGvdg&state=zlLtoo"],"Sec-Ch-Ua":["\"Chromium\";v=\"135\", \"Not-A.Brand\";v=\"8\""],"Dnt":["1"],"X-Copilotkit-Runtime-Client-Gql-Version":["1.8.5"],"X-Forwarded-For":["46.223.213.127"],"X-Forwarded-Ssl":["on"],"Content-Length":["209"],"Cookie":["REDACTED"],"Accept-Language":["en-GB,en-US;q=0.9,en;q=0.8"],"Content-Type":["application/json"],"Sec-Ch-Ua-Mobile":["?0"]}},"duration":0.829163942,"status":502,"err_id":"nxr9zs32h","err_trace":"reverseproxy.statusError (reverseproxy.go:1373)"}
                Apr 24 09:38:30 }
                Apr 24 09:38:30 }
                Apr 24 09:38:30 }
                Apr 24 09:38:31 2025-04-24 07:38:31,012 WARN exited: backend (exit status 1; not expected)
                Apr 24 09:38:32 2025-04-24 07:38:32,146 INFO spawned: 'backend' with pid 192
                Apr 24 09:38:33 2025-04-24T07:38:33Z
                Apr 24 09:38:33 2025-04-24T07:38:33Z
                Apr 24 09:38:33 2025-04-24 07:38:33,120 INFO success: backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
                Apr 24 09:38:33 > gitroom@0.0.0 start:prod
                Apr 24 09:38:33 > node dist/apps/backend/main.js
                

                After Postiz has restarted and I retry the redirect URL I get this error:

                51ab1d37-2516-4f45-8d64-6c08fddb62aa-image.png

                This is the redirect URL:

                https://postiz.claudron.OURSERVER.de/integrations/social/instagram?code=AQDvNogLUgbQ-BA....

                Not sure what to try next.

                BrutalBirdieB Offline
                BrutalBirdieB Offline
                BrutalBirdie
                Partner
                wrote on last edited by
                #8

                @perelin great writeup!
                This can be very useful.
                I see if I can figure something out from that.

                Do you have Matrix/Element, so we might connect? Since I am not looking forward setting up LinkedIn and instagram 😬

                Like my work? Consider donating a drink. Cheers!

                1 Reply Last reply
                1
                • perelinP Offline
                  perelinP Offline
                  perelin
                  wrote on last edited by
                  #9

                  Just Signal here, sorry 🙂 But happy to help. If Signal is fine I can send you my profile invite to contact@hackradt.com

                  BrutalBirdieB 1 Reply Last reply
                  0
                  • perelinP perelin

                    Just Signal here, sorry 🙂 But happy to help. If Signal is fine I can send you my profile invite to contact@hackradt.com

                    BrutalBirdieB Offline
                    BrutalBirdieB Offline
                    BrutalBirdie
                    Partner
                    wrote on last edited by
                    #10

                    @perelin yes Signal is fine for me as well.
                    Send it. 🙂

                    Like my work? Consider donating a drink. Cheers!

                    1 Reply Last reply
                    0
                    • avatar1024A Offline
                      avatar1024A Offline
                      avatar1024
                      wrote last edited by
                      #11

                      Hello, did this ever get resolved?

                      1 Reply Last reply
                      1
                      • D Offline
                        D Offline
                        Dont-Worry
                        wrote last edited by
                        #12

                        Not for me.

                        1 Reply Last reply
                        1
                        • visampV Offline
                          visampV Offline
                          visamp
                          wrote last edited by
                          #13

                          Same issue on my end. Appears that this app may not even work to add social accounts. Very odd

                          1 Reply Last reply
                          0
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes


                          • Login

                          • Don't have an account? Register

                          • Login or register to search.
                          • First post
                            Last post
                          0
                          • Categories
                          • Recent
                          • Tags
                          • Popular
                          • Bookmarks
                          • Search