Skype et Mattermost n'accèdent pas au web [Réglé]
mvt7 Membre non connecté
-
- Voir le profil du membre mvt7
- Inscrit le : 05/02/2019
- Groupes :
Voilà mon souci. Depuis la dernière mise à jour système (maj firefox, thunderbird et autre... d'ailleurs est-ce qu'on a un historiques des éléments mis à jour ?) les logiciels de messagerie instantanée n'accèdent plus à internet.
Mattermost dit
Citation :
Cannot connect to Mattermost
We're having trouble connecting to Mattermost. If refreshing this page (Ctrl+R or Command+R) does not work please verify that:
Your computer is connected to the internet.
The Mattermost URL https://mattermost.dockr.mycie.com/mycie is correct.
You can reach https://mattermost.dockr.mycie.com/mycie from a browser window.
ERR_PROXY_CONNECTION_FAILED (-130)
We're having trouble connecting to Mattermost. If refreshing this page (Ctrl+R or Command+R) does not work please verify that:
Your computer is connected to the internet.
The Mattermost URL https://mattermost.dockr.mycie.com/mycie is correct.
You can reach https://mattermost.dockr.mycie.com/mycie from a browser window.
ERR_PROXY_CONNECTION_FAILED (-130)
Evidemment lorsque j'essaie d'accéder à l'URL depuis le navigateur ça fonctionne.
Et skype dit
Citation :
Impossible de se connecter à internet
Voici le contenu de mon syslog quand j'ouvre Mattermost par exemple :
Code TEXT :
Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.gnome.ControlCenter.SearchProvider' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.gnome.Contacts.SearchProvider' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.gnome.Nautilus' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.gnome.Calculator.SearchProvider' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.gnome.clocks' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.gnome.Photos' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.gnome.clocks' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.gnome.Calculator.SearchProvider' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.gnome.ControlCenter.SearchProvider' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.gnome.Nautilus' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.freedesktop.Tracker1' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.gnome.Contacts.SearchProvider' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.freedesktop.Tracker1' Feb 22 14:18:26 localhost tracker-store[26929]: Cannot initialize database: Could not open sqlite3 database:'/home/moi/.cache/tracker/meta.db': bad parameter or other API misuse Feb 22 14:18:26 localhost dbus[928]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Feb 22 14:18:26 localhost dbus[928]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found. Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.freedesktop.Tracker1' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.freedesktop.Tracker1' Feb 22 14:18:26 localhost tracker-store[26943]: Cannot initialize database: Could not open sqlite3 database:'/home/moi/.cache/tracker/meta.db': bad parameter or other API misuse Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.gnome.Photos' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.freedesktop.Tracker1' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.freedesktop.Tracker1' Feb 22 14:18:26 localhost tracker-store[26961]: Cannot initialize database: Could not open sqlite3 database:'/home/moi/.cache/tracker/meta.db': bad parameter or other API misuse Feb 22 14:18:26 localhost nautilus[26899]: Could not establish a connection to Tracker: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.freedesktop.Tracker1' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.freedesktop.Tracker1' Feb 22 14:18:26 localhost tracker-store[26972]: Cannot initialize database: Could not open sqlite3 database:'/home/moi/.cache/tracker/meta.db': bad parameter or other API misuse Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.freedesktop.Tracker1' Feb 22 14:18:26 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.freedesktop.Tracker1' Feb 22 14:18:26 localhost tracker-store[26981]: Cannot initialize database: Could not open sqlite3 database:'/home/moi/.cache/tracker/meta.db': bad parameter or other API misuse Feb 22 14:18:26 localhost gnome-shell[5086]: Received error from DBus search provider org.gnome.Photos.desktop: Gio.IOErrorEnum: GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Feb 22 14:18:27 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.freedesktop.Tracker1' Feb 22 14:18:27 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.gnome.Photos' Feb 22 14:18:27 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.freedesktop.Tracker1' Feb 22 14:18:27 localhost tracker-store[27002]: Cannot initialize database: Could not open sqlite3 database:'/home/moi/.cache/tracker/meta.db': bad parameter or other API misuse Feb 22 14:18:27 localhost nautilus[26899]: Could not establish a connection to Tracker: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Feb 22 14:18:27 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.freedesktop.Tracker1' Feb 22 14:18:27 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.freedesktop.Tracker1' Feb 22 14:18:27 localhost tracker-store[27019]: Cannot initialize database: Could not open sqlite3 database:'/home/moi/.cache/tracker/meta.db': bad parameter or other API misuse Feb 22 14:18:27 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.freedesktop.Tracker1' Feb 22 14:18:27 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.freedesktop.Tracker1' Feb 22 14:18:27 localhost tracker-store[27029]: Cannot initialize database: Could not open sqlite3 database:'/home/moi/.cache/tracker/meta.db': bad parameter or other API misuse Feb 22 14:18:27 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.gnome.Photos' Feb 22 14:18:27 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.freedesktop.Tracker1' Feb 22 14:18:27 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.freedesktop.Tracker1' Feb 22 14:18:27 localhost tracker-store[27041]: Cannot initialize database: Could not open sqlite3 database:'/home/moi/.cache/tracker/meta.db': bad parameter or other API misuse Feb 22 14:18:27 localhost nautilus[26899]: Could not establish a connection to Tracker: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Feb 22 14:18:27 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.freedesktop.Tracker1' Feb 22 14:18:27 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.freedesktop.Tracker1' Feb 22 14:18:27 localhost tracker-store[27052]: Cannot initialize database: Could not open sqlite3 database:'/home/moi/.cache/tracker/meta.db': bad parameter or other API misuse Feb 22 14:18:27 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.freedesktop.Tracker1' Feb 22 14:18:27 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.freedesktop.Tracker1' Feb 22 14:18:27 localhost tracker-store[27062]: Cannot initialize database: Could not open sqlite3 database:'/home/moi/.cache/tracker/meta.db': bad parameter or other API misuse Feb 22 14:18:27 localhost /usr/libexec/gdm-wayland-session[5001]: Activating service name='org.freedesktop.Tracker1' Feb 22 14:18:27 localhost /usr/libexec/gdm-wayland-session[5001]: Successfully activated service 'org.freedesktop.Tracker1' Feb 22 14:18:27 localhost tracker-store[27071]: Cannot initialize database: Could not open sqlite3 database:'/home/moi/.cache/tracker/meta.db': bad parameter or other API misuse Feb 22 14:18:27 localhost gnome-shell[5086]: Received error from DBus search provider org.gnome.Photos.desktop: Gio.IOErrorEnum: GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Une idée ?
Merci d'avance
Édité par mvt7 Le 22/02/2019 à 14h22
mvt7 
Jybz Membre non connecté
-
- Voir le profil du membre Jybz
- Inscrit le : 10/10/2018
- Groupes :
-
Administrateur
-
Forgeron
Citation :
ERR_PROXY_CONNECTION_FAILED (-130)
mauvaise configuration ?
mvt7 Membre non connecté
-
- Voir le profil du membre mvt7
- Inscrit le : 05/02/2019
- Groupes :
Comment puis-je vérifier la configuration ?
mvt7
mvt7 Membre non connecté
-
- Voir le profil du membre mvt7
- Inscrit le : 05/02/2019
- Groupes :
mvt7
Jybz Membre non connecté
-
- Voir le profil du membre Jybz
- Inscrit le : 10/10/2018
- Groupes :
-
Administrateur
-
Forgeron
mvt7 :
C'est réglé, en fait mon networkManager était dead. et il embarquait une config proxy sortie du chapeau .
Ah voilà, désolé de ne pas avoir pu donner plus d'info, mais on n'en avait pas plus non plus, et c'était bien un défaut de configuration
Répondre
Vous n'êtes pas autorisé à écrire dans cette catégorie