Module cannot be installed with composer due to dependency issues

in my first post, I added a screenshot of the configuration
https://www.domaine.com
Watch the console in the inspector

no the domain is ok but it does not work

Here are the only informations I have

when I send messages, there is nothing in the logs

yes, it is installed

Before uninstalling it, the https://www.drupal.org/project/nodejs module has been configured like this and it works :

# nano nodejs.config.js

settings = {
  scheme: 'https',
  port: 8080,
  host: 'www.domaine.com',
  resource: '/socket.io',
  serviceKey: 'NhyYD3iP7kbES',
  backend: {
    port: 443,
    host: 'www.domaine.com',
    scheme: 'https',
    basePath: '',
    messagePath: '/nodejs/message'
  },
  debug: false,
  sslKeyPath: '',
  sslCertPath: '',
  sslCAPath: '',
  baseAuthPath: '/nodejs/',
  extensions: [],
  clientsCanWriteToChannels: false,
  clientsCanWriteToClients: false,
  transports: ['websocket', 'polling'],
  jsMinification: true,
  jsEtag: true,
  logLevel: 1
};

Does the configuration of nodeJS support the https ?

Where is the configuration in node_modules ?

It's weird that the webmaster is nothing to configure in node_modules

How is the backend managed?

Some site uses nodejs on a separate server. Would not it be advisable to configure node_modules manually with:

- serviceKey
- port
- host
- scheme

I updated #12

With my installation the backend uses port 443. Does your module support you?

This is the case of my configuration.

The node js server is on 8080

But the domain is on 443 (https)

So the module manages ports 80 and 443 for the backend ?

It is not possible.

I have apache header that requires secure connection.

Some browser blocks all unsecured urls

Ok thank you I will wait

maybe this question is related to this one ;

https://www.drupal.org/project/private_message/issues/2970962

Should it use the beta 4 or the dev.
I made the update Composer, but there is no config folder.

root@vps000000:/home/www.domaine.com/public_html/vendor/jaypan/private-message-nodejs# ls
app.js composer.json node_modules package.json package-lock.json README.md

How can I know the version?

- Updating drupal/vendor_stream_wrapper (1.0.0-beta2 => 1.0.0-beta3): DownloadDownloading (100%)
- Updating drupal/private_message_nodejs (1.0.0-beta3 => 1.0.0-beta4): DownloaDownloading (100%)

Here is what I did, but the "config" folder does not exist

The version is in 0.2 but he does not want to update

I can not update to beta 5. I'm trying to uninstall the module but I can not remove it from Composer

I found, you must manually delete the node_modules folder

Why compose install by defaul beta version 4 ?

I completely removed the module and installed it again with Composer.

He does not want to download the beta 5 and stays on the beta 4.

If I request the dev version I have the error in the screenshot.

that does not solve the problem

I think the module has not been properly uninstalled. I have this error message that prevents installation. What should I do ?

Unable to install Private Message, core.entity_form_display.message.private_message_notification.default, core.entity_view_display.message.private_message_notification.default, message.template.private_message_notification already exist in active configuration.

Can not reinstall the module. It displays #42

I found, there remained messages from the module "Message"

There is a problem, when the "Private Message" module is uninstalled, the message template in the "Message" module is not deleted.

I erased everything and checked that the files were erased. I cleaned the cace of "Composer", but it does not work ?

Thank you, the installation worked.

But I still have errors in the console. I do not understand why.

I added screenshots of my configuration.

It would be necessary for other people to test an https installation, to know if it comes from the module or my site. The funny thing is that with the drupal module nodejs integration, this configuration worked.

Ok, the red message is gone, but I still have:

DevTools failed to parse SourceMap: https://www.domaine.com/vendor_files/socket.io.js.map

Messages are not refreshed

Can you tell me if in the screenshots my configuration is correct?

Is there a delay to set to activate nodejs ?

There are no errors in /reports/dblog

How to be sure that the module is directly linked to the nodejs server?
There should be a message in the Drupal dashboard.

Yes, there is only the Private Message NodeJS module installed.

The warning appears only in Chrome. On Firefox there is no error, but I have to refresh the page manually to see the messages.

How can I know if the nodejs server communicates with the site?

OK ;-) I found. The secret does not match in the logs, when I send a message.

Yet, look at my previous screenshot, the secret is the same.

So the site communicates well with the nodejs server and the settings are correct.

There is a problem with the "secret"

It should also be added to the documentation the installation of PM2 which is essential to see the logs nodejs and maintain the connection

http://pm2.keymetrics.io/

It is very easy to install and use.

There are also two warning when I restart app.js I do not know if it concerns the module directly

I put a word in identical secret in drupal and it does not work

have you managed to reproduce the problem

The module does not seem to be working since the update. Pm2 logs are full of errors.

I have recreated the default.json file

There are no errors in the Drupal logs

I made the update to the beta 9. Here is the status of the module

I tested again and I still have the errors

Thank you. The message has changed but I still have the error and the secret. I made a copy paste and they are identical

delete

I did not understand steps 5 and 6. I uninstalled and installed the module to start over from the beginning. Can you tell me if the structure of the screenshots are correct ? Thank you

I tested with the configuration above, but I still have the secret problem

If I put a different secret, it shows on the dashboard that the server is misconfigured.

If I put an identical secret, it displays on the dashboard that the server is correctly configured.

But in the PM2 logs, it indicates that the secret does not match.

I have another problem. If I am authenticated, the site works. If I am anonymous, I have a blank page on the whole site with this message "The website encountered an unexpected error. Please try again later.".

See #73

Why is there a default.json file in config and another in private-message-nodejs?

Without PM2 it's the same result.

Do you know what is causing the problem #73 (If I disable the notification block, the error disappears.) ?

I do not understand, when I restart app.js it marks that he received the secret "mathieu".

If I send messages, it does not work anymore.

The beta version 10. How to know the version of the library ?
The library is on the same server as my site.

The version of the library could be displayed on the dashboard

This is version 0.3.6

The default.json file must be in the "config" folder only? It does not have to be as in private-message-nodejs ? #81

Ok. I do not see where the problem is with the secret. I have no error message.

I updated to beta 11 and I have the same error message. Do you know if other users have tested the module?

What should I do for the update. Should I delete manually folder?

delete

there is no error in the console

The problem is always the same. In the logs I see that he verifies and finds the secret and the second according to he verifies and no longer finds the secret.

In the dashboard, the status of "Private Message Node.js" is updated in real time.
But not the message of the thread.

Debugging is already enabled

Here is what I have :

https://www.domaine.com/modules/contrib/private_message_nodejs/js/privat...

/**
 * @file
 * Client-side script to integrate private message with browser notifications.
 */

/*global jQuery, Drupal, drupalSettings, io*/
/*jslint white:true, this, browser:true*/

(function ($, Drupal, drupalSettings, io) {

  "use strict";

  var initialized, browserNotificationSocket;

  function init() {

    // Only initialize once.
    if (!initialized) {
      initialized = true;

      browserNotificationSocket = io(drupalSettings.privateMessageNodejs.nodejsUrl + "/pm_browser_notification");

      Drupal.AjaxCommands.prototype.privateMessageNodejsNotifyBrowserOfNewMessage = function (ajax, response) {

        // For jSlint compatibility.
        ajax = ajax;
        $.each(response.uids, function (index) {
          browserNotificationSocket.emit("notify browser new message", response.uids[index], response.message);
        });
      };
    }
  }

  Drupal.behaviors.privateMessageNodejsForm = {
    attach: function () {
      init();
    }
  };

}(jQuery, Drupal, drupalSettings, io));

I drush cr every update. Why does the file remain in memory ?

I never had a problem with other libraries.

Do you have a command to update the cache ?

Thanks it works now ;-)
I erased the browser cache.