maeh

Domain > Limits & Settings > Limits > HTTP > default language for web client best regards, Markus

We're working with 15.5, so yes :) We updated from md5 to argon2. The argon2-Tool can be found here: https://github.com/P-H-C/phc-winner-argon2 #/bin/bash echo -n "Input Salt (16 Signs!): " read SALT echo -n "Input Password: " read PASS SALTX=$(echo $SALT | tr -d '\n' | xxd -p | awk '{print toupper($0)}') PASSX=$(echo -n…

Hello, we've managed to do that. We used the DB-Integration-Guide (https://documentation.solarwinds.com/archive/pdf/servu/serv-u_db_integration_guide.pdf). If needed, I can provide a working bash-script. best regards, Markus

Hello Jeff, neither 120.245.64.189 nor 221.4.215.215 belongs to www.labs.greynoise.io at public DNS. If Serv-U would do a reverse DNS-lookup, it wouldn't get the complete URL (https://www.labs.greynoise.io/grimoire/2024-06-solarwinds-serv-u/), but only the domain (www.labs.greynoise.io), so this doesn't seem to be a…

There is only one Hotfix for 15.4.2 or am I missing something? best regards, Markus

Hot Fix 1 for 15.4.2 is out and should address these problems: * Inconsistent HTTP session authentication when the password used contains special characters. * Group administrators can create access to restricted file system directories. * Sporadic failure to establish SSH connection under specific network conditions. *…

Hello, this part is good described in the Serv-U Administrator Guide (Point: "Create a Serv-U domain" respectively "Serv-U domain level settings / Listeners". In my Case, I use a separate IP for separate Domains, because not every protocol (for example SFTP) is able to handle more domains on one IP. best regards, Markus

Okay :) So, I would first be sure in your case, that the x-forwarded-for header is added correctly by the netscaler. Is it possible for you, to do a wireshark/tcpdump on the Serv-U Gateway to see the requests?

And with which protocol, your users are logging in? http(s) in browser or ftp(s)/sftp in ftp-client? best regards, Markus

Again: x-forwarded-for is useless for ftp-protocol. It's a http-protocol extension. best regards, Markus

Hi, x-forwarded-for is a http-protocol feature and doesn't work with ftp-connections. I don't know of any similar feature for ftp-protocol. this is not really a serv-u problem, but rather a global ftp-protocol problem. best regards, Markus

There is a extra location for feature requests: https://thwack.solarwinds.com/product-forums/serv-u-ftp-mft/i/feature-requests best regards, Markus

Just a small hint on this topic: Serv-U 15.4 seems to be released today, but until now, the changelog isn't updated - keep fingers crossed, everything will work in this version EDIT: Here they are: documentation.solarwinds.com/.../serv-u_15-4_release_notes.htm best regards, Markus

Updating all Components in one step seems risky in my opinion. Any usefull logs in the database-server? Can the new application-server connect to the old database-server? best regards, Markus

Hi Any news on this topic? Any answers from the support? thanks and best regards, Markus

Hello, I had to revert to 15.3.1 long time ago because of another problem (we have to implement Argon2-hashing for our Database-Users first), so I can't test the hotfix. Can you tell, if the fixed file from the BuddyDrop is replaced by the Hotfix or not? If not, it could be possible, that you have to revert to 15.3.2…

Serv-U 15.3.2 Hotfix is available and your work has been rewarded: ======================================== SolarWinds® Serv-U® 15.3.2 Hotfix 1 ======================================== This SolarWinds hotfix addresses the following issues: • OpenSSL upgraded to 3.0.8 • New Serv-U settings allowing non-RFC compliant SSH…

Could be Case 01005016, which is fixed in 15.3.1:

Normal behavior (as described in the Documentation) , but can be configured:

I think, 0.1.55 should be the last official version (or is http://www.jcraft.com/jsch/ also a fork?), but this is nothing to argue about :) I agree with you, that this should be an option in the "limits and settings"-Tab. best regards, Markus

Just for completeness and fairness, you have to say, that only JSCH 0.1.53 and 0.1.54 are affected. Newer clients are fixed.

Hello Jeff, Snapshots are definitely not needed to rollback. We had also the JSCH-0.1.54-Problem but could prove, that the client does the mistake in the connection process, so the customer updated his client and all went fine in this case. But: we had to rollback because of deactivating the possibility of storing…

Hello together, I've done some investigation in this task, because I had the same problem yesterday by updating my Serv-U from 15.3.1 to 15.3.2. For Testing, I installed two fresh Server-2019-VM: one in english and on in german. As I assumed, the problem is language-related: german Server 2019 english Server 2019 Perhaps,…

Just open a Support case. They will provide you fixed files. 

It's not the problem, when the Server is behind a loadbalancer or proxy. The problem occurs, when the Client is behind loadbalancer/proxy.

Thanks. Will you release a Hotfix for this problem, too?

They work after upgrade in the old web client, but the new web client isn't customizable in my opinion at this moment. I think, they will implement it later. Actually, the old web client is still working (and standard, if you connect).

Thanks for investigation. Does "related to loadbalancer" mean, that this problem only exists with loadbalancer enabled in Serv-U? I have this problem without any loadbalancer.