Hi Matthias ...
well, that's such a generic question / problem description. We usually need that full error log from the terminal to offer precise help. Anyway I would suggest that that customer is using our internal channel for requesting technical help by one of the SIMATIC service line colleagues for a deeper look.
Anyway : For all the others ... here are possible reasons, why you may face an error message not being able to log-in to the SIMATIC AX registry successfully:
0.1) Reminder: "Limited Sales Release"
SIMATIC AX currently is in a limited sales release phase and only available in selective countries only. This list of supported countries changes as time travels. Please get in contact with your Siemens sales representatives to check if the country you are in is in the list. Countries where AX is not official supported will not be able to login.
0.2) Reminder: "Prerequisites"
It is probably not the reason for that specific issue but we always recommend to ensure that you have installed latest Apax/AXCode and all the latest prerequisites. Please get that out of the scope before investigating issus in general.
1.) Company- and Firewall-settings
You may try to login within a restricted (secure) company network. Since most of SIMATIC AX contens are coming from the official online-(package)-registry you need to have an online access for initial activities (subscription-status, check for updates, loading packages etc.). This online access must be granted. Ensuring this for your AX workstations may require to involve your company IT section. SIMATIC AX is using 3rd party open source products, which also muss be allowed.
- allow access for the following domains: "siemens.io" / "https://console.simatic-ax.siemens.io"
- web-browsing-port "443" is open
- using "npm" and "node.js" is allowed
2.) Company CA and self-signed-certificates
Adding a company-CA could be helpful solving apax-connection issues.
Simply add an environment variable to your apax.yml which direct to your company ca cert pem file.
NODE_EXTRA_CA_CERTS = <path to ca pem file>Alternative you can add these env variable to your system later if that solves the issue. Since this is node.js related you may find a solution in the www as well.
For more information see:
https://nodejs.org/api/cli.html#node_extra_ca_certsfile
https://stackoverflow.com/questions/29283040/how-to-add-custom-certificate-authority-ca-to-nodejs
When using "Kaspersky Endpoint Security" or something similar, adding it's pem cert file to the environment variables may also be something to consider ... avoiding problems with self-signed-certificates-in-chain during apax usage.
3.) Check your active "Subscriptions"
SIMATIC AX is part of an user-based subscription business model. Visit your account settings and validate if you are still subscribed to the features and products you want to check-out. It could be the case that your trial version or active subscription expired. Get in contact with your community-account admin, who may connect an active subscription to your account if there are any free seat available or request new ones.
4.) Additional "Registries"
Login errors may also occur if your login-tokens from additional registries other than the @ax product scope expired or are required. Make sure you are successfully logged-in and your access-tokens / credentials are valid for all registries that are present in the apax.yml.
SIMATIC AX communiy scope on the github.pkg registry may be a common candidate.
5.) "Service currently unavailable"
In rare cases it can happen that the backend will be shut down temporary for maintenance.
Please always check back the live-ticker on the SIMATIC AX product page if available for more information.
... there may be more cases. Will add them to the post when we found out more.
You experienced a differnt reason? Shout out in the comments.
Keep going & happy coding ...
π±βπ» BEEP, BOOP, BEEP, BEEP, BOOP π±βπ
Thank you Stefan for the quick answer.