Setting up Customer Portal on 1.13

Hi Team
I am trying out the new version 1.13 on debian 12. The admin portal works fine, but the customer portal is NOT authenticating when username password is inputted.

Web version is 1.13.13-1
Customer portal version 1.13.4-1

Portal Nginx Content


server {
        listen 443 ssl;
        server_name customerportal.domain.com;
    ssl_certificate /etc/letsencrypt/live/customerportal.domain.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/customerportal.domain.com/privkey.pem; # managed by Certbot
        ssl_session_timeout 50m;
        ssl_session_cache builtin:1000;
        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;# SSLv3;
        ssl_ciphers  ECDHE-RSA-AES256-SHA384:AES256-SHA256:RC4:HIGH:!MD5:!aNULL:!eNULL:!NULL:!DH:!EDH:!AESGCM;
        add_header Strict-Transport-Security "max-age=31536000; includeSubdomains";
        ssl_prefer_server_ciphers   on;

        root /opt/yeti-client/dist;
        access_log /var/log/nginx/yeti-client.access.log;

}

server {
        listen 443 ssl;
        server_name customerapi.domain.com;
    ssl_certificate /etc/letsencrypt/live/customerapi.domain.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/customerapi.domain.com/privkey.pem; # managed by Certbot
        ssl_session_timeout 50m;
        ssl_session_cache builtin:1000;
        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;# SSLv3;
        ssl_ciphers  ECDHE-RSA-AES256-SHA384:AES256-SHA256:RC4:HIGH:!MD5:!aNULL:!eNULL:!NULL:!DH:!EDH:!AESGCM;
        add_header Strict-Transport-Security "max-age=31536000; includeSubdomains";
        ssl_prefer_server_ciphers   on;

        proxy_redirect off;
        proxy_set_header Host $host;
        proxy_set_header X-Proxy-Port $proxy_port;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $remote_addr;
        proxy_set_header HTTP_CLIENT_IP $remote_addr;
        proxy_set_header HTTP_X_FORWARDED_FOR $remote_addr;
        client_max_body_size        100m;
        client_body_buffer_size     128k;
        proxy_connect_timeout       100;
        proxy_send_timeout          20000;
        proxy_read_timeout          20000;
        proxy_buffer_size           32k;
        proxy_buffers               8 32k;
        proxy_busy_buffers_size     64k;
        proxy_temp_file_write_size  640k;

        allow all;

        location /api/rest/customer {
                allow all;
                proxy_pass  http://yeti-unicorn;

                if ($request_method = 'OPTIONS') {
                        add_header 'Access-Control-Allow-Origin' '*';
                        add_header 'Access-Control-Allow-Headers' 'Origin, X-Requested-With, Content-Type, Accept, api_key, Authorization';
                        add_header 'Access-Control-Allow-Methods' 'GET, POST, DELETE, PUT, PATCH, OPTIONS';
                        add_header 'Access-Control-Max-Age' 1728000;
                        add_header 'Content-Type' 'text/plain charset=UTF-8';
                        add_header 'Content-Length' 0;
                        return 204;
                }
                add_header 'Access-Control-Allow-Origin' '*';
                add_header 'Access-Control-Allow-Headers' 'Origin, X-Requested-With, Content-Type, Accept, api_key, Authorization';
                add_header 'Access-Control-Allow-Methods' 'GET, POST, DELETE, PUT, PATCH, OPTIONS';
                add_header 'Access-Control-Allow-Credentials' 'true';

        }

}

Content of /opt/yeti-client/dist/config.js

const YETI_CONFIG = {
  yeti: {
    apiBaseUrl: 'https://customerapi.domain.com',
    blockedPages: new Set([]),
    linkOnLogo: 'https://xxxxx.net/',
    pageTitle: 'xxxxx',
    locale: 'en',
  },
};

Chrome Logs shows that Auth to https://customerapi.domain.com/api/rest/customer/v1/auth is FAILING.

Please what could be wrong with the way I am setting it up?

You have to find why it “FAILING” or provide link where we can reproduce issue.

could you provide at least screenshot with error details?