Le portail est remplacé par le message "This is where Synapse is installed"

jln · April 15, 2024, 1:53pm

Bonjour,

Depuis un temps indéterminé, mon portail est remplacé par le message suivant :

"This is where Synapse is installed."

Je me suis rendu sur la page de configuration du domaine, j’ai sélectionné une “default app” quelconque avant de revenir au réglage normal (—), mais ça n’a rien changé.

Toutes les mises à jour sont faites, je tourne sur YunoHost 11.2.11.2, Synapse 1.104.0~ynh1, installés sur un serveur Kimsufi. Tous les services semblent tourner normalement.

Merci !

Pablo · April 15, 2024, 8:01pm

Bonjour,

Même problème chez moi.

Cordialement.

jln · April 15, 2024, 8:40pm

C’est résolu, j’ai déplacé Synapse sur son propre sous-domaine comme mentionné ici

Pablo · April 17, 2024, 9:48am

Bonjour,

J’ai également suivi le tuto:

création d’un sous domaine matrix.domaine.fr
publication de l’application synapse sur le sous domaine
re-génération des certificats pour le domaine et le sous domaine
→ Mes clients locaux se connectent sans soucis

Par contre, la fédération ne fonctionne plus: j’ai un problème de certificat (test avec federationtester)

x509: certificate is valid for matrix.domaine.fr, not domaine.fr

Dans les logs, j’ai des connections failures:

2024-04-17 11:21:39,356 - synapse.http.federation.matrix_federation_agent - 371 - INFO - federation_transaction_transmission_loop-26047- Failed to connect to davralin.work:8448: User timeout caused connection failure.
2024-04-17 11:21:39,356 - synapse.http.matrixfederationclient - 799 - INFO - federation_transaction_transmission_loop-26047- {PUT-O-15445} [davralin.work] Request failed: PUT matrix-federation://davralin.work/_matrix/federation/v1/send/1713338127471: TimeoutError(‘’)
2024-04-17 11:21:39,359 - synapse.http.federation.matrix_federation_agent - 371 - INFO - federation_transaction_transmission_loop-22957- Failed to connect to bagel.ninja:8448: User timeout caused connection failure.

J’ai passé toute la veille et ce matin à lire des forums et différentes docs sans succès. Ce ne doit pas être grand chose mais si quelqu’un a une piste, je lui en serai reconnaissant.

TheTrveAnthony · April 17, 2024, 11:05pm

Salut, j’ai eu ce problème aussi suite à une maj, j’ai généré un sous-domaine et déplacé synapse dessus, mais je ne plus m’y connecter maintenant, element indique que l’instance n’existe pas (j’ai tenté via un autre client web et j’ai la même erreur).

J’ai tenté cette solution sans succès. La doc mentionne un fichier .well-known à mettre à jour mais je ne sais pas où il est, quelqu’un sait comment régler ça, sans re-reinstaller synapse ?

merci

Josue · April 22, 2024, 9:05pm

Hello

Normalement pas besoin de gérer le ficher .well-know.

As tu essayé dans les clients de mettre comme adresse du serveur ton nouveau sous-domaine ?

TheTrveAnthony · April 23, 2024, 2:35am

Oui, le résultat est hélas le même (avec element desktop et cinny web)

Josue · April 23, 2024, 6:19am

Et si tu accède a https://son-sous-domaine.tld/_matrix/ ca te donne quoi ?

TheTrveAnthony · April 23, 2024, 1:53pm

Je tombe sur cette page (après plusieurs avertissements de sécurité de librewolf) :

Josue · April 23, 2024, 8:54pm

Ouais faudrait voir peut être avec element web et la console du navigateur ce qu’il dit si il y a des requête qui échouent et a quel uré.

TheTrveAnthony · April 23, 2024, 10:57pm

voilà les logs de la console :

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://purplehaze.noho.st/.well-known/matrix/client. (Reason: CORS request did not succeed). Status code: (null).

No response or error when parsing .well-known rageshake.ts:77:16
NetworkError when attempting to fetch resource. rageshake.ts:77:16
Error processing homeserver config: 
Object { state: "FAIL_PROMPT", error: "Invalid homeserver discovery response", base_url: null }
rageshake.ts:77:16
Attempted purplehaze.noho.st as a server_name but it failed Error: Failed to get autodiscovery configuration from server
    w languageHandler.tsx:92
    buildValidatedConfigFromDiscovery AutoDiscoveryUtils.tsx:272
    deriveData ServerPickerDialog.tsx:91
Caused by: "Invalid homeserver discovery response"
rageshake.ts:77:16
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://purplehaze.noho.st/_matrix/client/versions. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 302.

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://purplehaze.noho.st/_matrix/client/versions. (Reason: CORS request did not succeed). Status code: (null).

Invalid /versions response rageshake.ts:77:16
Error processing homeserver config: 
Object { state: "FAIL_ERROR", error: "Homeserver URL does not appear to be a valid Matrix homeserver", base_url: "https://purplehaze.noho.st" }
rageshake.ts:77:16
Error: Homeserver URL does not appear to be a valid Matrix homeserver
    w languageHandler.tsx:92
    buildValidatedConfigFromDiscovery AutoDiscoveryUtils.tsx:272
    validateServerConfigWithStaticUrls AutoDiscoveryUtils.tsx:200
Caused by: "Homeserver URL does not appear to be a valid Matrix homeserver"
rageshake.ts:77:16
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://matrix.purplehaze.noho.st/_matrix/client/versions. (Reason: CORS request did not succeed). Status code: (null).

Invalid /versions response rageshake.ts:77:16
Error processing homeserver config: 
Object { state: "FAIL_ERROR", error: "Homeserver URL does not appear to be a valid Matrix homeserver", base_url: "https://matrix.purplehaze.noho.st" }
rageshake.ts:77:16
Attempted purplehaze.noho.st as a server_name but it failed Error: Homeserver URL does not appear to be a valid Matrix homeserver
    w languageHandler.tsx:92
    buildValidatedConfigFromDiscovery AutoDiscoveryUtils.tsx:272
    deriveData ServerPickerDialog.tsx:91
Caused by: "Homeserver URL does not appear to be a valid Matrix homeserver"
rageshake.ts:77:16
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://purplehaze.noho.st/_matrix/client/versions. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 302.

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://purplehaze.noho.st/_matrix/client/versions. (Reason: CORS request did not succeed). Status code: (null).

Invalid /versions response rageshake.ts:77:16
Error processing homeserver config: 
Object { state: "FAIL_ERROR", error: "Homeserver URL does not appear to be a valid Matrix homeserver", base_url: "https://purplehaze.noho.st" }
rageshake.ts:77:16
Error: Homeserver URL does not appear to be a valid Matrix homeserver
    w languageHandler.tsx:92
    buildValidatedConfigFromDiscovery AutoDiscoveryUtils.tsx:272
    validateServerConfigWithStaticUrls AutoDiscoveryUtils.tsx:200
Caused by: "Homeserver URL does not appear to be a valid Matrix homeserver"
rageshake.ts:77:16
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://matrix.purplehaze.noho.st/_matrix/client/versions. (Reason: CORS request did not succeed). Status code: (null).

Invalid /versions response rageshake.ts:77:16
Error processing homeserver config: 
Object { state: "FAIL_ERROR", error: "Homeserver URL does not appear to be a valid Matrix homeserver", base_url: "https://matrix.purplehaze.noho.st" }
rageshake.ts:77:16
Attempted purplehaze.noho.st as a server_name but it failed Error: Homeserver URL does not appear to be a valid Matrix homeserver
    w languageHandler.tsx:92
    buildValidatedConfigFromDiscovery AutoDiscoveryUtils.tsx:272
    deriveData ServerPickerDialog.tsx:91
Caused by: "Homeserver URL does not appear to be a valid Matrix homeserver"
rageshake.ts:77:16
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://purplehaze.noho.st/_matrix/client/versions. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 302.

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://purplehaze.noho.st/_matrix/client/versions. (Reason: CORS request did not succeed). Status code: (null).

Invalid /versions response rageshake.ts:77:16
Error processing homeserver config: 
Object { state: "FAIL_ERROR", error: "Homeserver URL does not appear to be a valid Matrix homeserver", base_url: "https://purplehaze.noho.st" }
rageshake.ts:77:16
Error: Homeserver URL does not appear to be a valid Matrix homeserver
    w languageHandler.tsx:92
    buildValidatedConfigFromDiscovery AutoDiscoveryUtils.tsx:272
    validateServerConfigWithStaticUrls AutoDiscoveryUtils.tsx:200
Caused by: "Homeserver URL does not appear to be a valid Matrix homeserver"
rageshake.ts:77:16
Wait!
If someone told you to copy/paste something here, there is a high likelihood you're being scammed!
If you know what you're doing, Element is open-source, be sure to check out our GitHub (https://github.com/vector-im/element-web/) and contribute! rageshake.ts:83:8
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://matrix.purplehaze.noho.st/_matrix/client/versions. (Reason: CORS request did not succeed). Status code: (null).

Invalid /versions response rageshake.ts:77:16
Error processing homeserver config: 
Object { state: "FAIL_ERROR", error: "Homeserver URL does not appear to be a valid Matrix homeserver", base_url: "https://matrix.purplehaze.noho.st" }
rageshake.ts:77:16
Attempted purplehaze.noho.st as a server_name but it failed Error: Homeserver URL does not appear to be a valid Matrix homeserver
    w languageHandler.tsx:92
    buildValidatedConfigFromDiscovery AutoDiscoveryUtils.tsx:272
    deriveData ServerPickerDialog.tsx:91
    l Validation.tsx:164
    dA ServerPickerDialog.tsx:155
    validate Field.tsx:203
    p Field.tsx:190
    React 11
    unstable_runWithPriority scheduler.production.min.js:18
    React 3
Caused by: "Homeserver URL does not appear to be a valid Matrix homeserver"
rageshake.ts:77:16
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://purplehaze.noho.st/_matrix/client/versions. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 302.

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://purplehaze.noho.st/_matrix/client/versions. (Reason: CORS request did not succeed). Status code: (null).

Invalid /versions response rageshake.ts:77:16
Error processing homeserver config: 
Object { state: "FAIL_ERROR", error: "Homeserver URL does not appear to be a valid Matrix homeserver", base_url: "https://purplehaze.noho.st" }
rageshake.ts:77:16
Error: Homeserver URL does not appear to be a valid Matrix homeserver
    w languageHandler.tsx:92
    buildValidatedConfigFromDiscovery AutoDiscoveryUtils.tsx:272
    validateServerConfigWithStaticUrls AutoDiscoveryUtils.tsx:200
    deriveData ServerPickerDialog.tsx:108
    l Validation.tsx:164
    dA ServerPickerDialog.tsx:155
    validate Field.tsx:203
    p Field.tsx:190
    React 11
    unstable_runWithPriority scheduler.production.min.js:18
    React 3
Caused by: "Homeserver URL does not appear to be a valid Matrix homeserver"
rageshake.ts:77:16

Et en essayant avec le sous-domaine :

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://matrix.purplehaze.noho.st/.well-known/matrix/client. (Reason: CORS request did not succeed). Status code: (null).

No response or error when parsing .well-known rageshake.ts:77:16
NetworkError when attempting to fetch resource. rageshake.ts:77:16
Error processing homeserver config: 
Object { state: "FAIL_PROMPT", error: "Invalid homeserver discovery response", base_url: null }
rageshake.ts:77:16
Attempted matrix.purplehaze.noho.st as a server_name but it failed Error: Failed to get autodiscovery configuration from server
    w languageHandler.tsx:92
    buildValidatedConfigFromDiscovery AutoDiscoveryUtils.tsx:272
    deriveData ServerPickerDialog.tsx:91
    l Validation.tsx:164
    dA ServerPickerDialog.tsx:155
    validate Field.tsx:203
    dA ServerPickerDialog.tsx:165
    React 11
    unstable_runWithPriority scheduler.production.min.js:18
    React 3
Caused by: "Invalid homeserver discovery response"
rageshake.ts:77:16
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://matrix.purplehaze.noho.st/_matrix/client/versions. (Reason: CORS request did not succeed). Status code: (null).

Invalid /versions response rageshake.ts:77:16
Error processing homeserver config: 
Object { state: "FAIL_ERROR", error: "Homeserver URL does not appear to be a valid Matrix homeserver", base_url: "https://matrix.purplehaze.noho.st" }
rageshake.ts:77:16
Error: Homeserver URL does not appear to be a valid Matrix homeserver
    w languageHandler.tsx:92
    buildValidatedConfigFromDiscovery AutoDiscoveryUtils.tsx:272
    validateServerConfigWithStaticUrls AutoDiscoveryUtils.tsx:200
    deriveData ServerPickerDialog.tsx:108
    l Validation.tsx:164
    dA ServerPickerDialog.tsx:155
    validate Field.tsx:203
    dA ServerPickerDialog.tsx:165
    React 11
    unstable_runWithPriority scheduler.production.min.js:18
    React 3
Caused by: "Homeserver URL does not appear to be a valid Matrix homeserver"
rageshake.ts:77:16
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://matrix.purplehaze.noho.st/.well-known/matrix/client. (Reason: CORS request did not succeed). Status code: (null).

No response or error when parsing .well-known rageshake.ts:77:16
NetworkError when attempting to fetch resource. rageshake.ts:77:16
Error processing homeserver config: 
Object { state: "FAIL_PROMPT", error: "Invalid homeserver discovery response", base_url: null }
rageshake.ts:77:16
Attempted matrix.purplehaze.noho.st as a server_name but it failed Error: Failed to get autodiscovery configuration from server
    w languageHandler.tsx:92
    buildValidatedConfigFromDiscovery AutoDiscoveryUtils.tsx:272
    deriveData ServerPickerDialog.tsx:91
    l Validation.tsx:164
    dA ServerPickerDialog.tsx:155
    validate Field.tsx:203
    dA ServerPickerDialog.tsx:169
    React 11
    unstable_runWithPriority scheduler.production.min.js:18
    React 3
Caused by: "Invalid homeserver discovery response"
rageshake.ts:77:16
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://matrix.purplehaze.noho.st/_matrix/client/versions. (Reason: CORS request did not succeed). Status code: (null).

Invalid /versions response rageshake.ts:77:16
Error processing homeserver config: 
Object { state: "FAIL_ERROR", error: "Homeserver URL does not appear to be a valid Matrix homeserver", base_url: "https://matrix.purplehaze.noho.st" }
rageshake.ts:77:16
Error: Homeserver URL does not appear to be a valid Matrix homeserver
    w languageHandler.tsx:92
    buildValidatedConfigFromDiscovery AutoDiscoveryUtils.tsx:272
    validateServerConfigWithStaticUrls AutoDiscoveryUtils.tsx:200
    deriveData ServerPickerDialog.tsx:108
    l Validation.tsx:164
    dA ServerPickerDialog.tsx:155
    validate Field.tsx:203
    dA ServerPickerDialog.tsx:169
    React 11
    unstable_runWithPriority scheduler.production.min.js:18
    React 3
Caused by: "Homeserver URL does not appear to be a valid Matrix homeserver"
rageshake.ts:77:16
    t rageshake.ts:77
    <anonymous> logger.ts:97
    deriveData ServerPickerDialog.tsx:111
    l Validation.tsx:164
    dA ServerPickerDialog.tsx:155
    validate Field.tsx:203
    dA ServerPickerDialog.tsx:169
    React 11
    unstable_runWithPriority scheduler.production.min.js:18
    React 3
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://matrix.purplehaze.noho.st/.well-known/matrix/client. (Reason: CORS request did not succeed). Status code: (null).

No response or error when parsing .well-known rageshake.ts:77:16
NetworkError when attempting to fetch resource. rageshake.ts:77:16
Error processing homeserver config: 
Object { state: "FAIL_PROMPT", error: "Invalid homeserver discovery response", base_url: null }
rageshake.ts:77:16
Attempted matrix.purplehaze.noho.st as a server_name but it failed Error: Failed to get autodiscovery configuration from server
    w languageHandler.tsx:92
    buildValidatedConfigFromDiscovery AutoDiscoveryUtils.tsx:272
    deriveData ServerPickerDialog.tsx:91
    l Validation.tsx:164
    dA ServerPickerDialog.tsx:155
    validate Field.tsx:203
    p Field.tsx:190
    React 11
    unstable_runWithPriority scheduler.production.min.js:18
    React 3
Caused by: "Invalid homeserver discovery response"
rageshake.ts:77:16
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://matrix.purplehaze.noho.st/_matrix/client/versions. (Reason: CORS request did not succeed). Status code: (null).

Invalid /versions response rageshake.ts:77:16
Error processing homeserver config: 
Object { state: "FAIL_ERROR", error: "Homeserver URL does not appear to be a valid Matrix homeserver", base_url: "https://matrix.purplehaze.noho.st" }
rageshake.ts:77:16
Error: Homeserver URL does not appear to be a valid Matrix homeserver
    w languageHandler.tsx:92
    buildValidatedConfigFromDiscovery AutoDiscoveryUtils.tsx:272
    validateServerConfigWithStaticUrls AutoDiscoveryUtils.tsx:200
    deriveData ServerPickerDialog.tsx:108
    l Validation.tsx:164
    dA ServerPickerDialog.tsx:155
    validate Field.tsx:203
    p Field.tsx:190
    React 11
    unstable_runWithPriority scheduler.production.min.js:18
    React 3
Caused by: "Homeserver URL does not appear to be a valid Matrix homeserver"

Josue · April 24, 2024, 8:43pm

Ce qui m’intéresse surtout c’est l’onglet network de la console avec la requête qui va vers le serveur synapse et la réponse.

TheTrveAnthony · April 24, 2024, 8:56pm

Ok désolé, j’ai pas du tout l’habitude d’utiliser cet outil,

Avec le domanine principal :

Avec le sous-domaine :

Josue · April 24, 2024, 9:30pm

As tu activité la fonctionnalité sliding proxy ? Et depuis quel client et quel URL essaye tu de te connecter ?

Vu le log il semble que ton client essaye de se connecter avec sliding proxy ce qui n’est probablement pas supporté par ton serveur sauf si tu as mis a jours depuis la branche matrixv2.

TheTrveAnthony · April 24, 2024, 9:44pm

As tu activité la fonctionnalité sliding proxy ?

Non, et d’ailleurs je n’en ai jamais entendu parler… (et j’ai jamais fait de manip particulière non plus)

Et depuis quel client et quel URL essaye tu de te connecter ?

Sur les screenshot, c’était via https://app.element.io, et en temps normal sur element desktop.

Pour la maj, je la fais en ssh avec yunohost app upgrade donc je suppose que c’est via la branche master ?

Josue · April 25, 2024, 6:14am

Petite question est ce normal que tu n’a pas mis let’s encrpyt sur ton domaine ou synapse fonctionne ?

Ca peut peut être être la raisons des problèmes.

TheTrveAnthony · April 25, 2024, 2:47pm

J’avais crée le sous-domaine en ssh sans active let’s encrypt en effet, tout refonctionne maintenant, merci pour ton aide !