You are not logged in.
Pages: 1
For some time now it has not been possible to access the GLPI network and, in particular, the marketplace.
When activating the debug mode, the following error message appears:
Resolving timed out after 5515 milliseconds
I am not behind a proxy.
Thank you and best regards
Offline
If you have command-line access on your GLPI server, can you try using curl to try and contact the GLPI Network URL directly and see what the result is?
curl --head https://services.glpi-network.com/
The error you are seeing makes me think that the issue lays outside of GLPI. With the curl command you should see the response headers from the server and the first line should indicate a 200 OK status. If that works OK, then I would suggest checking if you have a "config/local_define.php" or "inc/downstream.php" file present in your GLPI installation and that neither have set a GLPI_NETWORK_* variable to something different to what you see in "inc/based_config.php". The based_config file is the default configuration file that sets some environment variables that determine things like folder locations and various URLs. "config/local_define.php" is the file that can be used to override the default environment variables in a specific environment while "inc/downstream.php" can be used by distributors (package maintainers) to set defaults for their distribution.
GLPI_NETWORK_SERVICES should be https://services.glpi-network.com by default.
GLPI_NETWORK_REGISTRATION_API_URL should be {GLPI_NETWORK_SERVICES}/api/registration/ by default.
GLPI_MARKETPLACE_PLUGINS_API_URI should be {GLPI_NETWORK_SERVICES}/api/glpi-plugins/ by default.
GLPI Collaborator and Plugin Developer.
My non-English comments are automated translations. Sorry for any confusion that causes.
Mes commentaires non anglais sont des traductions automatiques. Désolé pour toute confusion qui cause.
Mis comentarios que no están en inglés son traducciones automáticas. Perdón por cualquier confusión que cause.
Offline
Try to browse https: //services.glpi-network.com/api/glpi-plugins/ and you will get a 404 error
The same happens with https: //services.glpi-network.com/api/registration/.
Offline
The 404 on those API endpoints is normal. I think it is just because you don't send your registration key in the request. If the GLPI server cannot view the base URL though, then it is not resolving the domain name for some reason. Preferably this would be done using curl and not a browser as GLPI would use curl in the background for these requests too.
GLPI Collaborator and Plugin Developer.
My non-English comments are automated translations. Sorry for any confusion that causes.
Mes commentaires non anglais sont des traductions automatiques. Désolé pour toute confusion qui cause.
Mis comentarios que no están en inglés son traducciones automáticas. Perdón por cualquier confusión que cause.
Offline
My server has no restrictions on outgoing on the Internet. Anyway, I tested it as you suggested:
curl --head https://services.glpi-network.com
HTTP/1.1 200 OK
Date: Thu, 05 May 2022 07:25:24 GMT
Server: Apache
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
X-Content-Type-Options: nosniff
Cache-Control: no-cache, private
Set-Cookie: XSRF-TOKEN=eyJpdiI6IlpWNzd4NHVHQWdQVXBUQXJ5dVFnYkE9PSIsInZhbHVlIjoiTVh3eHZGaG5RN25heUJFYUVpM3VLMFFISDZOSE56emJra2Qrak56d0hrRnlzN0wrcEtXcEV5OThyZUlDcHJGakxPY1lDV2RWL3ZzOTVNTDBwVXJ6ZzM5SFU3TXVPKzY1c0RtK011RlQ0dTZSeXBKU1lMa25GVzhkZmU2cHdhdEIiLCJtYWMiOiI4Mzc1MDUwNjA0N2IyZjY4MTFiM2RkMGFlOGMwZDViOGQyY2I5ODZmY2NhODk3YzVmNDZlMGM5ZjU0Y2E3Y2RmIiwidGFnIjoiIn0%3D; expires=Thu, 05-May-2022 09:25:24 GMT; Max-Age=7200; path=/; samesite=lax
Set-Cookie: glpi_network_session=eyJpdiI6IjROeElzYW83QjI4Q2hBL1hMN0cvNXc9PSIsInZhbHVlIjoidnhPS1R2TURWQkFoaDlBUzFxZmxyTUI0SnVhKzlHK2xHS2dVZjJaeGdXWS8zcU8xY2c0MzBIWmFKeFFSM3BiMjhSSUdvWXN0bnYzc01nWnhoS1liWGpjRGpNWk9odFlZNkdtMmR6ZEgzN2hBK3hYb2k5MXM5SkQ0N3FkUXZHSy8iLCJtYWMiOiJiZjVhNWEzMmYzMjgxOTdmNjQ4ZjZhMGQyMGFjNjQyY2Y4MTgxOTViZmE0YmJhMDViNDllNWU0ZDkzMmMwMmRmIiwidGFnIjoiIn0%3D; expires=Thu, 05-May-2022 09:25:24 GMT; Max-Age=7200; path=/; httponly; samesite=lax
Content-Type: text/html; charset=UTF-8
and as you can see it has no problems in reaching that URL.
I also run on my web root:
grep -r "GLPI_NETWORK_" *
inc/based_config.php: 'GLPI_NETWORK_MAIL' => 'glpi@teclib.com',
inc/based_config.php: 'GLPI_NETWORK_SERVICES' => 'https://services.glpi-network.com', // GLPI Network services project URL
inc/based_config.php: 'GLPI_NETWORK_REGISTRATION_API_URL' => '{GLPI_NETWORK_SERVICES}/api/registration/',
inc/based_config.php: 'GLPI_MARKETPLACE_PLUGINS_API_URI' => '{GLPI_NETWORK_SERVICES}/api/glpi-plugins/',
install/update.php: 'glpinetwork_url' => GLPI_NETWORK_SERVICES,
src/GLPINetwork.php: "<a href='" . GLPI_NETWORK_SERVICES . "'>" . sprintf(__('Register on %1$s!'), 'GLPI Network') . "</a><br>" .
src/GLPINetwork.php: rtrim(GLPI_NETWORK_REGISTRATION_API_URL, '/') . '/info',
src/GLPINetwork.php: "<a href='" . GLPI_NETWORK_SERVICES . "' target='_blank'>" . GLPI_NETWORK_SERVICES . "</a>"
src/GLPINetwork.php: "<a href='" . GLPI_NETWORK_SERVICES . "' target='_blank'>" . GLPI_NETWORK_SERVICES . "</a>"
src/GLPINetwork.php: $content = \Toolbox::callCurl(GLPI_NETWORK_REGISTRATION_API_URL, [], $error_msg, $curl_error);
src/GLPINetwork.php: rtrim(GLPI_NETWORK_REGISTRATION_API_URL, '/') . '/offers',
src/Marketplace/View.php: "<a href='" . GLPI_NETWORK_SERVICES . "'>" . sprintf(__('Register on %1$s'), 'GLPI Network') . "</a> "
src/Marketplace/View.php: "<a href='" . GLPI_NETWORK_SERVICES . "'>" . sprintf(__('Renew it on %1$s.'), 'GLPI Network') . "</a> "
src/Marketplace/View.php: $networkmail = GLPI_NETWORK_MAIL;
src/Marketplace/View.php: $buttons .= "<a href='" . GLPI_NETWORK_SERVICES . "' target='_blank'>
src/Marketplace/View.php: <a href='" . GLPI_NETWORK_SERVICES . "' target='_blank'
src/Marketplace/View.php: <a href='" . GLPI_NETWORK_SERVICES . "' target='_blank'
and I have a valid registration key set in my setup.
What else could it be?
Thank you for your time.
Offline
I also checked if the problem was related to SELinux:
getsebool httpd_can_network_connect
httpd_can_network_connect --> on
I don't really know what else to do.
Offline
Nobody can help?
Offline
I find it strange that I am the only one with this problem.
Offline
I have the same probelm. Need to help.
Thanks.
Giang.
Offline
Pages: 1