user endpoint doesn't return after adding certificate

[imduchy]

Version

module: 4.9.1
nuxt: 2.14.12

mode:

• universal
• spa

Nuxt configuration

  auth: {
    cookie: {
      options: {
        maxAge: 432000, // 5 days
      },
    },
    redirect: {
      login: '/login',
      logout: '/login',
      home: '/',
    },
    strategies: {
      local: {
        endpoints: {
          login: {
            url: '/auth/login',
            method: 'post',
            propertyName: false,
          },
          logout: {
            url: '/auth/logout',
            method: 'get',
          },
          user: {
            url: '/auth/users',
            method: 'get',
            propertyName: false,
          },
        },
        tokenRequired: false,
        tokenType: false,
      },
    },
  },

Reproduction

⚠️ without a minimal reproduction we won't be able to look into your issue

What is expected?

The user endpoint should return a user object. req.user should be set when accessing the /user endpoint.

What is actually happening?

The user endpoint, after logging in, returns empty body when accessing via custom domain (myapp.com) with a SSL certificate from Certbot. But when accessing via Azure's domain (myapp.azurewebsites.net), everything works. The req.user object is undefined on user endpoint, but correctly set on login endpoint.

// update: Got the same issue with an SSL certificate issued by ZeroSSL

Steps to reproduce

1. Access the website via custom domain
2. Log-in
3. nothing happens

As mentioned above, the same application works when accessed via Azure's domain.
Repo: https://github.com/Duchynko/tipovacka

Additional information

I tried to add a plugin with rejectUnauthorized as mentioned here, but this doesn't seem to work.
nuxt/nuxt#6559 (comment)

Checklist

• I have tested with the latest Nuxt version and the issue still occurs
• I have tested with the latest module version and the issue still occurs
• I have searched the issue tracker and this issue hasn't been reported yet

[imduchy]

Seems like the same issue was mentioned here

#437 (comment)