Cannot install pro via NPM (was working before) and client page is broken

Licensing
#1

Hi,

We have been installing our pro license via yarn for a while without any problems, but it’s failing today. This is really urgent as it’s required for our deployment process.

yarn install v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
error An unexpected error occurred: "http://npm.webix.com/@xbs%2fwebix-pro/-/webix-pro-10.2.4.tgz: aborted".
info If you think this is a bug, please open a bug report with the information provided in "/builds/xxx/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Additionally, we cannot access the client page. https://webix.com/clients/ renders a white page only in both Firefox and Chrome.

Are you aware of a problem and do you know when it will be fixed? This is very urgent for us.

Thank you.

#2

It’s working again now (both the client area and NPM). Thank you for fixing it.

1 Like
#3

Hello @violuke ,

I’m glad to hear that the functionality is restored for you.
Thank you for your report. It helped us to quickly react to the issue.

1 Like
#4

This is happening again. I think your security certificate has expired as your main website is also down. Can this please be urgently fixed?

#5

Hello @violuke
The certificate is updated, and the access to packages should be fully restored now.
Apologies for the inconvinience caused by the issue.

1 Like
#6

This is happening again. And https://webix.com/clients/ is down again.

Please can this be resolved promptly? This unreliability is really making us question if Webix is the right partner for us :frowning_face:

verbose 1.403405083 Request "https://npm.webix.com/@xbs%2fpasmat" finished with status code 200.
verbose 1.434785208 Request "https://registry.yarnpkg.com/jet-hotkey" finished with status code 200.
verbose 1.435150542 Request "https://registry.yarnpkg.com/jet-restate" finished with status code 200.
verbose 1.455794125 Request "https://registry.yarnpkg.com/webix-jet" finished with status code 200.
[2/4] 🚚  Fetching packages...
verbose 1.641953708 Performing "GET" request to "https://npm.webix.com/@xbs%2fwebix-pro/-/webix-pro-10.2.5.tgz".
verbose 1.645240625 Performing "GET" request to "https://npm.webix.com/@xbs%2fpivot/-/pivot-10.2.5.tgz".
info There appears to be trouble with your network connection. Retrying...
verbose 5.121400208 Performing "GET" request to "https://npm.webix.com/@xbs%2fwebix-pro/-/webix-pro-10.2.5.tgz".
verbose 5.12551325 Performing "GET" request to "https://npm.webix.com/@xbs%2fpivot/-/pivot-10.2.5.tgz".
info There appears to be trouble with your network connection. Retrying...
verbose 9.009127 Performing "GET" request to "https://npm.webix.com/@xbs%2fwebix-pro/-/webix-pro-10.2.5.tgz".
verbose 9.011822667 Performing "GET" request to "https://npm.webix.com/@xbs%2fpivot/-/pivot-10.2.5.tgz".
info There appears to be trouble with your network connection. Retrying...
verbose 12.891225208 Performing "GET" request to "https://npm.webix.com/@xbs%2fpivot/-/pivot-10.2.5.tgz".
verbose 12.895563083 Performing "GET" request to "https://npm.webix.com/@xbs%2fwebix-pro/-/webix-pro-10.2.5.tgz".
info There appears to be trouble with your network connection. Retrying...
verbose 16.799974583 Performing "GET" request to "https://npm.webix.com/@xbs%2fpivot/-/pivot-10.2.5.tgz".
verbose 16.801762458 Performing "GET" request to "https://npm.webix.com/@xbs%2fwebix-pro/-/webix-pro-10.2.5.tgz".
verbose 17.691362833 Error: aborted
    at TLSSocket.socketCloseListener (node:_http_client:460:19)
    at TLSSocket.emit (node:events:531:35)
    at node:net:337:12
    at TCP.done (node:_tls_wrap:657:7)
error Error: aborted
    at TLSSocket.socketCloseListener (node:_http_client:460:19)
    at TLSSocket.emit (node:events:531:35)
    at node:net:337:12
    at TCP.done (node:_tls_wrap:657:7)
#7

Resolved now, thank you.

#8

Hello and sorry for the inconvinience.
I can confirm that prior to your report, there was an update on our server. Some services were relaunched and it could cause a short-term unavailability of our resources.

#9

We experienced downtime of almost an hour; this doesn’t sound like restarting services to me - it sounds like a problem that went unnoticed.

I understand the need to update and that this can cause brief interruptions, but we rely on you and so would appreciate testing updates better to ensure they haven’t caused problems, or at least a status page/announcement letting us know that you’re aware that the update went wrong and working on it.

Thank you.