Search found 7 matches
- Fri Apr 23, 2021 3:43 pm
- Forum: Knowledge Center
- Topic: JCE cannot authenticate the provider BC
- Replies: 0
- Views: 90821
JCE cannot authenticate the provider BC
The error java.lang.SecurityException: JCE cannot authenticate the provider BC at javax.crypto.Cipher.getInstance(Unknown Source) has been reported after applying PTF Group SF99730 Level 20310 . The update breaks PGP encryption/decryption. Other issues around encryption/ciphers may be encountered wi...
- Tue Sep 08, 2020 5:38 pm
- Forum: Knowledge Center
- Topic: PKIX path building failed
- Replies: 1
- Views: 71816
Re: PKIX path building failed
If you’re receiving a PKIX error when attempting to connect to outlook.office365.com, the GoAnywhere support team has identified two Globalsign certificates that may be missing from the key vault or trust store. These two Globalsign certificates have been attached for your convenience. After the cer...
- Fri Sep 13, 2019 4:18 pm
- Forum: Knowledge Center
- Topic: SFTP client download using Cyber Duck fails with "illegal offset when working on encypted folder"
- Replies: 0
- Views: 28832
SFTP client download using Cyber Duck fails with "illegal offset when working on encypted folder"
When a web user's files are located in an encrypted folder, file uploads/downloads can not be resumed. By default, Cyber Duck is configured to segment file downloads with multiple connections per file. This setting must be disabled (Edit > preferences > Transfers) in Cyber Duck in order to successfu...
- Fri Jul 05, 2019 4:48 pm
- Forum: Knowledge Center
- Topic: Newly Configured REST Server resource fails with 400 or “It is not on the appropriate screen or unknown” error
- Replies: 0
- Views: 11859
Newly Configured REST Server resource fails with 400 or “It is not on the appropriate screen or unknown” error
In some older versions of REST server implementations, authentication is transmitted preemptively opposed to when a client connects to the server, and the server asks the client to login. In this scenario, the REST server requires authentication to occur in a request header upon connection. In order...
- Thu Jun 13, 2019 9:14 am
- Forum: Knowledge Center
- Topic: SAML Single Sign On - No RelayState parameter found
- Replies: 0
- Views: 15404
SAML Single Sign On - No RelayState parameter found
This error on the screen or in the GoAnywhere.log indicates the SAML ID Provider (IDP) is not providing a relayState parameter. This parameter is needed in GA MFT and is part of the SAML specification. The relayState parameter is meant to indicate where the user should end up after authenticating wi...
- Mon Apr 01, 2019 4:24 pm
- Forum: Knowledge Center
- Topic: Why Does My Newly Configured SFTP Resource Hang Indefinitely?
- Replies: 0
- Views: 11025
Why Does My Newly Configured SFTP Resource Hang Indefinitely?
Question: I have just set up a new SFTP Server resource and when I test it, the resource just hangs/spins without ever receiving a response. Why is this happening? Answer: By default, the SFTP client/resource is not configured to use a specific authentication method; therefore, when negotiating the...
- Fri Mar 29, 2019 4:35 pm
- Forum: Knowledge Center
- Topic: What to do if GoAnywhere is failing to start?
- Replies: 0
- Views: 15667
What to do if GoAnywhere is failing to start?
Clustered Environments: 1. If the GoAnywhere service is failing to start, the first place to look is the Tomcat logs. Tomcat logs (from each server) [installDir]/goanywhere/tomcat/logs/Catalina.out If running on Windows , look for: Commons-Daemon(ceationDate).log Stderr(ceationDate).log Stdout(ceat...