New 13.1 and 14.1 available... Release notes as well. security bulletin to be released soon (support.citrix.com/support-home/kbsearch/article?articleNumber=…)

Spare a screenshot for the "The article is no longer available or you are not authorised to view it." of us? ;D

link shuld be live soon

Yep, available now, thanks. ^_^

ADM WAF protecting these? Or firmware update only for them.

firmware update

@Eric, thanks for the confirmation of what I was thinking ;-)

See this a lot in PreChecks Certificate digest verification failed. This may indicate missing or tampered certificate/key files.

Can't wait.. :D

We have updated several gateways and other ADCs to 13.1-63.18. No problem at all so far.

For appliances NOT using HTTP Strict Profiles, the default value is 0, and in that case, merely upgrading to the builds containing the fix WILL NOT address the vulnerability completely. In this case, customers must manually set Http2SmallWndTimeout to 30 seconds. Please note that Http2SmallWndTimeout is a new parameter and is only available in the firmware builds that contain the fix.

No problems on 14.1 yet either, so far. Hoping it continues that way for everyone. =D

How's everyone handling the timing of their upgrades this round? We generally tend to err on the side of "ASAP just in case", but given there isn't one on the level of unauthenticated RCE, are you waiting for standard maintenance windows? I get that it probably depends on your line of work and all that, just curious. We're at least doing our test and secondary datacenter instances right now.

Is the thought that all http profiles should be set to 30 seconds for Http2SmallWndTimeout? If all HTTP Strict profiles have it by default and non HTTP Strict should be change to 30, am i missing another type of HTTP profile that should not be 30?

We are going into a holiday weekend in the US so I am not waiting for standard maintenance.

I killed my gateway, ssl error when trying to access the NS gateway after upgrading to 13.1 latest ... We have to drive to our data center to fail it over. Careful. I did the NS internal one before and no prob. Not sure what happened here.

We upgraded a 14.1 test HA pair and a standalone 14.1 VPX in our secondary site without issue.

Had 1 client that Oauth didn't work after upgrade. NTP needed to sync.

I have an ERR_SSL_PROTOCOL_ERROR when attempting to access it. Another service, std vip works on same NS

No issues here with the 13.1 upgrade.

No issues here, 13.1 and 14.1 pairs, all done W/ Console secondary delay

The issue was on me, the current GW private key was overwritten with the new one, bad luck 😕

I need to asterisk my previous statement that all our 14.1 standalone/HA VPX upgrades completed without issue....all of them had to reactivate LAS via NetScaler Console after the upgrade, went into grace period as Premium 20 after the upgrade completed. Believe we also had to do that back in March, but maybe it's something unique to our config causing it.

Hmm, thank you for the heads up, I'll have to double check the ones I did yesterday to make sure. 🤪

License error in NS GUI is that it couldn't reach the license server, static/PBR's look like they should allow it, and it works fine with configured through NS Console but definitely could be on our end.

7GB free now!?!?! i can't delete any more files

Did you already delete old versions from /var/nsinstall ?

While upgrading our secondary HA node from 13.1-59.22 to 13.1-63.18, we received warnings like the following: Checking if portal core files are modified Checksum failed for the following files. /var/netscaler/logon/themes/Default/homepage.html: FAILED /var/netscaler/logon/themes/Default/resources/fr.xml: FAILED /var/netscaler/logon/themes/Default/resources/ja.xml: FAILED [...] /var/netscaler/logon/themes/Greenbubble/homepage.html: FAILED /var/netscaler/logon/themes/Greenbubble/resources/fr.xml: FAILED /var/netscaler/logon/themes/Greenbubble/resources/ja.xml: FAILED [...] The upgrade completed seemingly successfully, but upon failover to the upgraded node, all our Citrix Virtual Apps and Desktops sessions became disconnected. During previous failovers, sessions have disconnected and reconnected almost immediately.

Noticed that failover issue on the last upgrade too. @Melissa Nelson yes, and core, crash, nstrace, and deleted all tar.gz files im nslog. I opened a case to see what my options are on a 2nd drive. Its an AWS instance.

We've had to increase our VPXs' disk space as we kept running out. (We tried adding another disk, but that may have only helped with /var/crash - I can't remember.) I believe most of my notes were cribbed from this article: community.citrix.com/techzone-blogs/netscaler/manually-adjust-netscaler-vpx-disk-space

this one is on AWS, doesn't look like expanding is an option, we'll see what support says

Too many chats, which one to pick.. Had my first issue post-patchning! Unable to create RDP (and I'm sure other) bookmarks, with the Gateway WAF enabled. APPFW APPFW_SCHEMA_PARAMETER_INVALID 91013 0 : 92.39.46.191 1518818-PPE0 - ns-web-default-appfw-profile Parameter is invalid as per API Spec: (ns-web-spec) for Endpoint: POST x.x/vpns/portal/scripts/newbm.pl) <blocked> Works when disabled, of course. The fix was to enable the following, after that, bookmarks and WAF works together again. bind appfw profile ns-web-default-appfw-profile -restValidation "POST:/vpns/portal/scripts/newbm.pl"

Existing bookmarks still continue to work though?

My testaccount did, yeah. But the user complained that theirs didn't, not sure if it was a "unable to add new ones!" or user error, looked like a new-ish user.

Hmm ok. Haven't heard any complaints with existing RDP bookmarks yet but I did the 13.1 patch

fyi, circling back on the AWS instance expansion, we were able to get the drives expanded....had to do it live as the serial console didn't work

13.1 got (another) build, 63.19. I'm unsure which thread is best so posting in the original one, but, hopefully it'll fix whatever problems people have with 63.18. • Build 13.1-63.19 replaces Build 13.1-63.18. • Build 13.1-63.19 includes the following fixes, along with the enhancements and fixes available in Build 13.1-63.18: NSHELP-43998 and NSHELP-44288.