Postiz•2mo ago

Ticket: Postiz login issue after SMTP setup on Synology NAS

@Ketseum Just created a ticket
Question: I installed Postiz on my Synology NAS using Docker Compose on Portainer. I used a custom SMTP server instead of Google because Google was returning 400 errors indicating that the Username and Password were not accepted. Now that the emails are working fine and I’ve verified the email successfully, I am unable to log in. There are no visible errors or logs; when I attempt to log in, the page just reloads with empty inputs, returning me to the login screen.
Attempted: Configured a custom SMTP server since Google was rejecting my credentials. Verified that the email configuration is functional, and I received the verification email successfully. Tried logging in multiple times with the correct credentials but encountered the same issue where the page reloads without logging in. Checked Docker logs and Postiz logs for errors but found nothing apparent.
Working On: I am trying to set up Postiz for email communication and task management on my Synology NAS. The primary goal is to ensure proper authentication and usability.
Using Postiz On: I am using Docker-Compose on Portainer.
Take it from here @Postiz

6 Replies

SupportOP•2mo ago

@Postiz please help @Ketseum

Ketseum•2mo ago

I don't know if it's help but I have

{
  "message": "Cannot GET /auth/login",
  "error": "Not Found",
  "statusCode": 404
}

{
  "message": "Cannot GET /auth/login",
  "error": "Not Found",
  "statusCode": 404
}

https://postiz.domain.me/api/auth/login

https://postiz.domain.me/api/auth/login

and also this new log :

{

  accepted: [ '[email protected]' ],

  rejected: [],



[

    'SIZE 262144000',

    '8BITMIME',

    'PIPELINING',

    'PIPECONNECT',

    'AUTH PLAIN LOGIN',

    'HELP'

  ],

  envelopeTime: 92,

  messageTime: 96,

  messageSize: 2515,

  response: '250 OK id=1tPTBq-001HYP-2K',

  envelope: { from: '[email protected]', to: [ '[email protected]' ] },

  messageId: '<[email protected]>'

}

[Nest] 153  - 12/22/2024, 9:08:56 PM   ERROR [ExceptionsHandler] Converting circular structure to JSON

    --> starting at object with constructor 'Socket'

    |     property 'parser' -> object with constructor 'HTTPParser'

    --- property 'socket' closes the circle

TypeError: Converting circular structure to JSON

    --> starting at object with constructor 'Socket'

    |     property 'parser' -> object with constructor 'HTTPParser'

    --- property 'socket' closes the circle

    at JSON.stringify (<anonymous>)

    at stringify (/app/node_modules/express/lib/response.js:1160:12)

    at ServerResponse.json (/app/node_modules/express/lib/response.js:271:14)

    at ExpressAdapter.reply (/app/node_modules/@nestjs/platform-express/adapters/express-adapter.js:62:62)

    at RouterResponseController.apply (/app/node_modules/@nestjs/core/router/router-response-controller.js:15:36)

    at /app/node_modules/@nestjs/core/router/router-execution-context.js:176:48

    at async /app/node_modules/@nestjs/core/router/router-execution-context.js:47:13

    at async /app/node_modules/@nestjs/core/router/router-proxy.js:9:17

{

  accepted: [ '[email protected]' ],

  rejected: [],



[

    'SIZE 262144000',

    '8BITMIME',

    'PIPELINING',

    'PIPECONNECT',

    'AUTH PLAIN LOGIN',

    'HELP'

  ],

  envelopeTime: 92,

  messageTime: 96,

  messageSize: 2515,

  response: '250 OK id=1tPTBq-001HYP-2K',

  envelope: { from: '[email protected]', to: [ '[email protected]' ] },

  messageId: '<[email protected]>'

}

[Nest] 153  - 12/22/2024, 9:08:56 PM   ERROR [ExceptionsHandler] Converting circular structure to JSON

    --> starting at object with constructor 'Socket'

    |     property 'parser' -> object with constructor 'HTTPParser'

    --- property 'socket' closes the circle

TypeError: Converting circular structure to JSON

    --> starting at object with constructor 'Socket'

    |     property 'parser' -> object with constructor 'HTTPParser'

    --- property 'socket' closes the circle

    at JSON.stringify (<anonymous>)

    at stringify (/app/node_modules/express/lib/response.js:1160:12)

    at ServerResponse.json (/app/node_modules/express/lib/response.js:271:14)

    at ExpressAdapter.reply (/app/node_modules/@nestjs/platform-express/adapters/express-adapter.js:62:62)

    at RouterResponseController.apply (/app/node_modules/@nestjs/core/router/router-response-controller.js:15:36)

    at /app/node_modules/@nestjs/core/router/router-execution-context.js:176:48

    at async /app/node_modules/@nestjs/core/router/router-execution-context.js:47:13

    at async /app/node_modules/@nestjs/core/router/router-proxy.js:9:17

and this is my stack :

services:
  db:
    image: postgres:17
    container_name: Postiz-DB
    hostname: postiz-db
    mem_limit: 1g
    cpu_shares: 1024
    security_opt:
      - no-new-privileges:true
    healthcheck:
      test: ["CMD", "pg_isready", "-q", "-d", "postiz", "-U", "postizuser"]
      timeout: 45s
      interval: 10s
      retries: 10
    volumes:
      - /volume1/docker/postiz/db:/var/lib/postgresql/data:rw
    environment:
      POSTGRES_DB: postiz
      POSTGRES_USER: postizuser
      POSTGRES_PASSWORD: postizpass
    restart: on-failure:5

  postiz:
    image: ghcr.io/gitroomhq/postiz-app:latest
    container_name: Postiz
    restart: on-failure:5
    environment:
      MAIN_URL: "https://postiz.domain.me"
      FRONTEND_URL: "https://postiz.domain.me"
      NEXT_PUBLIC_BACKEND_URL: "https://postiz.domain.me/api"
      BACKEND_INTERNAL_URL: http://localhost:3000
      JWT_SECRET: mykey
      EMAIL_PROVIDER: "nodemailer"
      EMAIL_HOST: "CONFIDENTIAL"
      EMAIL_PORT: "465"
      EMAIL_SECURE: "true"
      EMAIL_USER: "CONFIDENTIAL"
      EMAIL_FROM_NAME: "CONFIDENTIAL"
      EMAIL_FROM_ADDRESS: "CONFIDENTIAL"
      EMAIL_PASS: "CONFIDENTIAL"
      DATABASE_URL: postgresql://postizuser:postizpass@postiz-db:5432/postiz
      REDIS_URL: redis://postiz-redis:6379
      IS_GENERAL: true
      STORAGE_PROVIDER: local
      UPLOAD_DIRECTORY: /uploads
      NEXT_PUBLIC_UPLOAD_DIRECTORY: /uploads
    volumes:
      - /volume1/docker/postiz/config:/config/:rw
      - /volume1/docker/postiz/uploads:/uploads/:rw
    ports:
      - 5488:5000
    depends_on:
      db:
        condition: service_healthy
      redis:
        condition: service_healthy
        
  redis:
    image: redis:7.2
    container_name: Postiz-REDIS
    restart: on-failure:5
    healthcheck:
      test: redis-cli ping
      interval: 10s
      timeout: 3s
      retries: 3
    volumes:
      - /volume1/docker/postiz/redis:/data:rw

services:
  db:
    image: postgres:17
    container_name: Postiz-DB
    hostname: postiz-db
    mem_limit: 1g
    cpu_shares: 1024
    security_opt:
      - no-new-privileges:true
    healthcheck:
      test: ["CMD", "pg_isready", "-q", "-d", "postiz", "-U", "postizuser"]
      timeout: 45s
      interval: 10s
      retries: 10
    volumes:
      - /volume1/docker/postiz/db:/var/lib/postgresql/data:rw
    environment:
      POSTGRES_DB: postiz
      POSTGRES_USER: postizuser
      POSTGRES_PASSWORD: postizpass
    restart: on-failure:5

  postiz:
    image: ghcr.io/gitroomhq/postiz-app:latest
    container_name: Postiz
    restart: on-failure:5
    environment:
      MAIN_URL: "https://postiz.domain.me"
      FRONTEND_URL: "https://postiz.domain.me"
      NEXT_PUBLIC_BACKEND_URL: "https://postiz.domain.me/api"
      BACKEND_INTERNAL_URL: http://localhost:3000
      JWT_SECRET: mykey
      EMAIL_PROVIDER: "nodemailer"
      EMAIL_HOST: "CONFIDENTIAL"
      EMAIL_PORT: "465"
      EMAIL_SECURE: "true"
      EMAIL_USER: "CONFIDENTIAL"
      EMAIL_FROM_NAME: "CONFIDENTIAL"
      EMAIL_FROM_ADDRESS: "CONFIDENTIAL"
      EMAIL_PASS: "CONFIDENTIAL"
      DATABASE_URL: postgresql://postizuser:postizpass@postiz-db:5432/postiz
      REDIS_URL: redis://postiz-redis:6379
      IS_GENERAL: true
      STORAGE_PROVIDER: local
      UPLOAD_DIRECTORY: /uploads
      NEXT_PUBLIC_UPLOAD_DIRECTORY: /uploads
    volumes:
      - /volume1/docker/postiz/config:/config/:rw
      - /volume1/docker/postiz/uploads:/uploads/:rw
    ports:
      - 5488:5000
    depends_on:
      db:
        condition: service_healthy
      redis:
        condition: service_healthy
        
  redis:
    image: redis:7.2
    container_name: Postiz-REDIS
    restart: on-failure:5
    healthcheck:
      test: redis-cli ping
      interval: 10s
      timeout: 3s
      retries: 3
    volumes:
      - /volume1/docker/postiz/redis:/data:rw

also I check my database, my user is create

chandu•2mo ago

Hi I am trying to set up postiz using docker compose. I have the application running and would now like to register a user. I understand the default set up comes with a mail server that intercepts the registration emails. Does anyone know what port it runs on? I am not able to find this in the documentation. I'd appreciate any inputs you can give me.

zapoqx•2mo ago

unfortunately, I don't believe you'll be helped. Several of us have that same issue and it always stops the same way on the request since October. Also had pleas to make it more verbose to figure out why that return to login happens, but nothing and I've tried many things based on their docs. Only "solution" seems to be make a localhost server (so you always connect by localhost:5000). I feel that is a separate question, but I always knew it as you needed your own smtp server. The mailer is just to connect.

Ketseum•2mo ago

@Nevo David can you help on this?

zapoqx•4w ago

Someone else found the issue. I'm assuming you're using a synology.me domain. It seems one person added a merge request where the issue is the program is not accepting some 2nd-level subdomains, in this cases, whatever the subdomain you made for name.synology.me (i.e. postiz.name.synology.me), it is stopping at the first subdomain which is why it won't login correctly. Would be waiting for approval, but it seems the temp fix is force a Primary subdomain somewhere else if possible until the code is approved to fix.

Gaming

Programming

Ticket: Postiz login issue after SMTP setup on Synology NAS

Did you find this page helpful?