|
liam
|
|
|
Group: Forum Members
Posts: 12,
Visits: 85
|
+x+x+x+x+x+x+x+x2025-01-13 17:18:17,475 INFO - com.hsbc.gltc.reg.sftp.Sftp - XXD-SFTPSFTP09I ThreadGroup0Fail to connect to ftp site:HKW00108370.hk.hsbc.Try to 3 times. 2025-01-13 17:18:17,475 FATAL - com.hsbc.gltc.reg.sftp.Sftp - XXD-SFTPSFTP01E ThreadGroup0:Fail to connect to SFTP. Detail:The connection did not complete: The connection did not complete: The connection did not complete: The connection did not complete Hello, I recommend that you perform the upgrade without updating the settings. Make a simple test connection on the server, "sftp localhost" from a command prompt on the server. If that connection goes through, then make the settings changes one step at a time. It is possible that the settings import is setting an invalid valid for the new version, causing the connection to fail. Did you open a cmd window and type sftp localhost? The connection failed. Did you do this immediately after the upgrade and before the configuration import?  Yes, I just uninstalled and reinstalled So you are getting the error "request for subsystem 'sftp' failed". This error can be caused by user restrictions to the sftp subsystem or the sftp process itself. Please check our event log, accessible from the Logging page of the Local Server Configuration program, for any error events from FortressSFTP. You can also check the application event log for any Application Manager events. It is possible that the the path settings were corrupted when you imported the Build 9 settings. Keep in mind that if you are using the older settings export/import, which creates a .pfcg file, the installation location must be in the exact same location, otherwise the applications will not be found.   那这该如何解决呢 Please check the following on the Local Server Configuration program: On the Access Control page that the Allow SFTP access checkbox is checked On the SFTP Users page that either your user is listed or the checkbox to “Only allow configured users..” is unchecked. On the SFTP Groups page that either your user is one of the configured groups or the checkbox to “Only allow configured groups…” is unchecked. Where is the .pfcg file stored?
|
|
|
|
|
liam
|
|
|
Group: Forum Members
Posts: 12,
Visits: 85
|
+x+x+x+x+x+x+x+x2025-01-13 17:18:17,475 INFO - com.hsbc.gltc.reg.sftp.Sftp - XXD-SFTPSFTP09I ThreadGroup0Fail to connect to ftp site:HKW00108370.hk.hsbc.Try to 3 times. 2025-01-13 17:18:17,475 FATAL - com.hsbc.gltc.reg.sftp.Sftp - XXD-SFTPSFTP01E ThreadGroup0:Fail to connect to SFTP. Detail:The connection did not complete: The connection did not complete: The connection did not complete: The connection did not complete Hello, I recommend that you perform the upgrade without updating the settings. Make a simple test connection on the server, "sftp localhost" from a command prompt on the server. If that connection goes through, then make the settings changes one step at a time. It is possible that the settings import is setting an invalid valid for the new version, causing the connection to fail. Did you open a cmd window and type sftp localhost? The connection failed. Did you do this immediately after the upgrade and before the configuration import?  Yes, I just uninstalled and reinstalled So you are getting the error "request for subsystem 'sftp' failed". This error can be caused by user restrictions to the sftp subsystem or the sftp process itself. Please check our event log, accessible from the Logging page of the Local Server Configuration program, for any error events from FortressSFTP. You can also check the application event log for any Application Manager events. It is possible that the the path settings were corrupted when you imported the Build 9 settings. Keep in mind that if you are using the older settings export/import, which creates a .pfcg file, the installation location must be in the exact same location, otherwise the applications will not be found.   那这该如何解决呢 Please check the following on the Local Server Configuration program: On the Access Control page that the Allow SFTP access checkbox is checked On the SFTP Users page that either your user is listed or the checkbox to “Only allow configured users..” is unchecked. On the SFTP Groups page that either your user is one of the configured groups or the checkbox to “Only allow configured groups…” is unchecked. Now our client cannot connect to the new version of pragma fortress ssh. How to add diffie-hellman-group1-sha1? Key exchange not found  In addition, I found the sshd_config file, which is a .lnk file. How do I open it?
|
|
|
|
|
Technical Support Group...
|
|
|
Group: Moderators
Posts: 144,
Visits: 648
|
+x+x+x+x+x+x+x+x+x2025-01-13 17:18:17,475 INFO - com.hsbc.gltc.reg.sftp.Sftp - XXD-SFTPSFTP09I ThreadGroup0Fail to connect to ftp site:HKW00108370.hk.hsbc.Try to 3 times. 2025-01-13 17:18:17,475 FATAL - com.hsbc.gltc.reg.sftp.Sftp - XXD-SFTPSFTP01E ThreadGroup0:Fail to connect to SFTP. Detail:The connection did not complete: The connection did not complete: The connection did not complete: The connection did not complete Hello, I recommend that you perform the upgrade without updating the settings. Make a simple test connection on the server, "sftp localhost" from a command prompt on the server. If that connection goes through, then make the settings changes one step at a time. It is possible that the settings import is setting an invalid valid for the new version, causing the connection to fail. Did you open a cmd window and type sftp localhost? The connection failed. Did you do this immediately after the upgrade and before the configuration import?  Yes, I just uninstalled and reinstalled So you are getting the error "request for subsystem 'sftp' failed". This error can be caused by user restrictions to the sftp subsystem or the sftp process itself. Please check our event log, accessible from the Logging page of the Local Server Configuration program, for any error events from FortressSFTP. You can also check the application event log for any Application Manager events. It is possible that the the path settings were corrupted when you imported the Build 9 settings. Keep in mind that if you are using the older settings export/import, which creates a .pfcg file, the installation location must be in the exact same location, otherwise the applications will not be found.   那这该如何解决呢 Please check the following on the Local Server Configuration program: On the Access Control page that the Allow SFTP access checkbox is checked On the SFTP Users page that either your user is listed or the checkbox to “Only allow configured users..” is unchecked. On the SFTP Groups page that either your user is one of the configured groups or the checkbox to “Only allow configured groups…” is unchecked. Now our client cannot connect to the new version of pragma fortress ssh. How to add diffie-hellman-group1-sha1? Key exchange not found  In addition, I found the sshd_config file, which is a .lnk file. How do I open it?  Hello, You are viewing help files on OpenSSH. We are not OpenSSH, so configuration and release notes are not relevant. You can enable sha1 key exchange algorotihm using the Local Server Configuration program -> General Settings -> Key Exchange page.
Pragma Systems Technical Support 13809 Research Blvd, #675 Austin, TX 78750 http://www.pragmasys.com
|
|
|
|
|
liam
|
|
|
Group: Forum Members
Posts: 12,
Visits: 85
|
+x+x+x+x+x+x+x+x+x+x2025-01-13 17:18:17,475 INFO - com.hsbc.gltc.reg.sftp.Sftp - XXD-SFTPSFTP09I ThreadGroup0Fail to connect to ftp site:HKW00108370.hk.hsbc.Try to 3 times. 2025-01-13 17:18:17,475 FATAL - com.hsbc.gltc.reg.sftp.Sftp - XXD-SFTPSFTP01E ThreadGroup0:Fail to connect to SFTP. Detail:The connection did not complete: The connection did not complete: The connection did not complete: The connection did not complete Hello, I recommend that you perform the upgrade without updating the settings. Make a simple test connection on the server, "sftp localhost" from a command prompt on the server. If that connection goes through, then make the settings changes one step at a time. It is possible that the settings import is setting an invalid valid for the new version, causing the connection to fail. Did you open a cmd window and type sftp localhost? The connection failed. Did you do this immediately after the upgrade and before the configuration import?  Yes, I just uninstalled and reinstalled So you are getting the error "request for subsystem 'sftp' failed". This error can be caused by user restrictions to the sftp subsystem or the sftp process itself. Please check our event log, accessible from the Logging page of the Local Server Configuration program, for any error events from FortressSFTP. You can also check the application event log for any Application Manager events. It is possible that the the path settings were corrupted when you imported the Build 9 settings. Keep in mind that if you are using the older settings export/import, which creates a .pfcg file, the installation location must be in the exact same location, otherwise the applications will not be found.   那这该如何解决呢 Please check the following on the Local Server Configuration program: On the Access Control page that the Allow SFTP access checkbox is checked On the SFTP Users page that either your user is listed or the checkbox to “Only allow configured users..” is unchecked. On the SFTP Groups page that either your user is one of the configured groups or the checkbox to “Only allow configured groups…” is unchecked. Now our client cannot connect to the new version of pragma fortress ssh. How to add diffie-hellman-group1-sha1? Key exchange not found  In addition, I found the sshd_config file, which is a .lnk file. How do I open it?  Hello, You are viewing help files on OpenSSH. We are not OpenSSH, so configuration and release notes are not relevant. You can enable sha1 key exchange algorotihm using the Local Server Configuration program -> General Settings -> Key Exchange page.  It has been enabled, but the client still cannot connect, and I cannot see the client connection record in the event view  The client seems to be a Java environment. This is the error message of the client.
|
|
|
|
|
Technical Support Group...
|
|
|
Group: Moderators
Posts: 144,
Visits: 648
|
+x+x+x+x+x+x+x+x+x2025-01-13 17:18:17,475 INFO - com.hsbc.gltc.reg.sftp.Sftp - XXD-SFTPSFTP09I ThreadGroup0Fail to connect to ftp site:HKW00108370.hk.hsbc.Try to 3 times. 2025-01-13 17:18:17,475 FATAL - com.hsbc.gltc.reg.sftp.Sftp - XXD-SFTPSFTP01E ThreadGroup0:Fail to connect to SFTP. Detail:The connection did not complete: The connection did not complete: The connection did not complete: The connection did not complete Hello, I recommend that you perform the upgrade without updating the settings. Make a simple test connection on the server, "sftp localhost" from a command prompt on the server. If that connection goes through, then make the settings changes one step at a time. It is possible that the settings import is setting an invalid valid for the new version, causing the connection to fail. Did you open a cmd window and type sftp localhost? The connection failed. Did you do this immediately after the upgrade and before the configuration import?  Yes, I just uninstalled and reinstalled So you are getting the error "request for subsystem 'sftp' failed". This error can be caused by user restrictions to the sftp subsystem or the sftp process itself. Please check our event log, accessible from the Logging page of the Local Server Configuration program, for any error events from FortressSFTP. You can also check the application event log for any Application Manager events. It is possible that the the path settings were corrupted when you imported the Build 9 settings. Keep in mind that if you are using the older settings export/import, which creates a .pfcg file, the installation location must be in the exact same location, otherwise the applications will not be found.   那这该如何解决呢 Please check the following on the Local Server Configuration program: On the Access Control page that the Allow SFTP access checkbox is checked On the SFTP Users page that either your user is listed or the checkbox to “Only allow configured users..” is unchecked. On the SFTP Groups page that either your user is one of the configured groups or the checkbox to “Only allow configured groups…” is unchecked. Where is the .pfcg file stored? The .pfcg file is not created as part of the installation. It is generated when you manually use the Legacy Setting export on the Configuration Management page of the Local Server Configuration program. You would pick the location at that time. I do not recommend using the .pfcg file as it does have limitations when importing to the server. If you are using the Settings export/import, then you should use the XML option. The .pfcg file is not part of the settings other than for import. It is not loaded during execution in any way.
Pragma Systems Technical Support 13809 Research Blvd, #675 Austin, TX 78750 http://www.pragmasys.com
|
|
|
|
|
liam
|
|
|
Group: Forum Members
Posts: 12,
Visits: 85
|
+x+x+x+x+x+x+x+x+x+x2025-01-13 17:18:17,475 INFO - com.hsbc.gltc.reg.sftp.Sftp - XXD-SFTPSFTP09I ThreadGroup0Fail to connect to ftp site:HKW00108370.hk.hsbc.Try to 3 times. 2025-01-13 17:18:17,475 FATAL - com.hsbc.gltc.reg.sftp.Sftp - XXD-SFTPSFTP01E ThreadGroup0:Fail to connect to SFTP. Detail:The connection did not complete: The connection did not complete: The connection did not complete: The connection did not complete Hello, I recommend that you perform the upgrade without updating the settings. Make a simple test connection on the server, "sftp localhost" from a command prompt on the server. If that connection goes through, then make the settings changes one step at a time. It is possible that the settings import is setting an invalid valid for the new version, causing the connection to fail. Did you open a cmd window and type sftp localhost? The connection failed. Did you do this immediately after the upgrade and before the configuration import?  Yes, I just uninstalled and reinstalled So you are getting the error "request for subsystem 'sftp' failed". This error can be caused by user restrictions to the sftp subsystem or the sftp process itself. Please check our event log, accessible from the Logging page of the Local Server Configuration program, for any error events from FortressSFTP. You can also check the application event log for any Application Manager events. It is possible that the the path settings were corrupted when you imported the Build 9 settings. Keep in mind that if you are using the older settings export/import, which creates a .pfcg file, the installation location must be in the exact same location, otherwise the applications will not be found.   那这该如何解决呢 Please check the following on the Local Server Configuration program: On the Access Control page that the Allow SFTP access checkbox is checked On the SFTP Users page that either your user is listed or the checkbox to “Only allow configured users..” is unchecked. On the SFTP Groups page that either your user is one of the configured groups or the checkbox to “Only allow configured groups…” is unchecked. Where is the .pfcg file stored? The .pfcg file is not created as part of the installation. It is generated when you manually use the Legacy Setting export on the Configuration Management page of the Local Server Configuration program. You would pick the location at that time. I do not recommend using the .pfcg file as it does have limitations when importing to the server. If you are using the Settings export/import, then you should use the XML option. The .pfcg file is not part of the settings other than for import. It is not loaded during execution in any way. OK, I have been using XML import and export
|
|
|
|
|
liam
|
|
|
Group: Forum Members
Posts: 12,
Visits: 85
|
+x+x+x+x+x+x+x+x+x+x2025-01-13 17:18:17,475 INFO - com.hsbc.gltc.reg.sftp.Sftp - XXD-SFTPSFTP09I ThreadGroup0Fail to connect to ftp site:HKW00108370.hk.hsbc.Try to 3 times. 2025-01-13 17:18:17,475 FATAL - com.hsbc.gltc.reg.sftp.Sftp - XXD-SFTPSFTP01E ThreadGroup0:Fail to connect to SFTP. Detail:The connection did not complete: The connection did not complete: The connection did not complete: The connection did not complete Hello, I recommend that you perform the upgrade without updating the settings. Make a simple test connection on the server, "sftp localhost" from a command prompt on the server. If that connection goes through, then make the settings changes one step at a time. It is possible that the settings import is setting an invalid valid for the new version, causing the connection to fail. Did you open a cmd window and type sftp localhost? The connection failed. Did you do this immediately after the upgrade and before the configuration import?  Yes, I just uninstalled and reinstalled So you are getting the error "request for subsystem 'sftp' failed". This error can be caused by user restrictions to the sftp subsystem or the sftp process itself. Please check our event log, accessible from the Logging page of the Local Server Configuration program, for any error events from FortressSFTP. You can also check the application event log for any Application Manager events. It is possible that the the path settings were corrupted when you imported the Build 9 settings. Keep in mind that if you are using the older settings export/import, which creates a .pfcg file, the installation location must be in the exact same location, otherwise the applications will not be found.   那这该如何解决呢 Please check the following on the Local Server Configuration program: On the Access Control page that the Allow SFTP access checkbox is checked On the SFTP Users page that either your user is listed or the checkbox to “Only allow configured users..” is unchecked. On the SFTP Groups page that either your user is one of the configured groups or the checkbox to “Only allow configured groups…” is unchecked. Where is the .pfcg file stored? The .pfcg file is not created as part of the installation. It is generated when you manually use the Legacy Setting export on the Configuration Management page of the Local Server Configuration program. You would pick the location at that time. I do not recommend using the .pfcg file as it does have limitations when importing to the server. If you are using the Settings export/import, then you should use the XML option. The .pfcg file is not part of the settings other than for import. It is not loaded during execution in any way. Do you have any suggestions for my connection error?
|
|
|
|
|
Technical Support Group...
|
|
|
Group: Moderators
Posts: 144,
Visits: 648
|
+x+x+x+x+x+x+x+x+x+x+x2025-01-13 17:18:17,475 INFO - com.hsbc.gltc.reg.sftp.Sftp - XXD-SFTPSFTP09I ThreadGroup0Fail to connect to ftp site:HKW00108370.hk.hsbc.Try to 3 times. 2025-01-13 17:18:17,475 FATAL - com.hsbc.gltc.reg.sftp.Sftp - XXD-SFTPSFTP01E ThreadGroup0:Fail to connect to SFTP. Detail:The connection did not complete: The connection did not complete: The connection did not complete: The connection did not complete Hello, I recommend that you perform the upgrade without updating the settings. Make a simple test connection on the server, "sftp localhost" from a command prompt on the server. If that connection goes through, then make the settings changes one step at a time. It is possible that the settings import is setting an invalid valid for the new version, causing the connection to fail. Did you open a cmd window and type sftp localhost? The connection failed. Did you do this immediately after the upgrade and before the configuration import?  Yes, I just uninstalled and reinstalled So you are getting the error "request for subsystem 'sftp' failed". This error can be caused by user restrictions to the sftp subsystem or the sftp process itself. Please check our event log, accessible from the Logging page of the Local Server Configuration program, for any error events from FortressSFTP. You can also check the application event log for any Application Manager events. It is possible that the the path settings were corrupted when you imported the Build 9 settings. Keep in mind that if you are using the older settings export/import, which creates a .pfcg file, the installation location must be in the exact same location, otherwise the applications will not be found.   那这该如何解决呢 Please check the following on the Local Server Configuration program: On the Access Control page that the Allow SFTP access checkbox is checked On the SFTP Users page that either your user is listed or the checkbox to “Only allow configured users..” is unchecked. On the SFTP Groups page that either your user is one of the configured groups or the checkbox to “Only allow configured groups…” is unchecked. Where is the .pfcg file stored? The .pfcg file is not created as part of the installation. It is generated when you manually use the Legacy Setting export on the Configuration Management page of the Local Server Configuration program. You would pick the location at that time. I do not recommend using the .pfcg file as it does have limitations when importing to the server. If you are using the Settings export/import, then you should use the XML option. The .pfcg file is not part of the settings other than for import. It is not loaded during execution in any way. Do you have any suggestions for my connection error? I suggest you use Server Operation Logging on the server side to collect information as to why the client is failing. Go to the Logging page on the Local Server Configuration program. Turn on Server Operation Logging and set the level to 6. Configure a directory for the log files. I recommend a directory outside of the Program Files directory. Make sure that the ssh users have write access to the configured directory. Run a test where the user fails to logon. Review the log file for any error statements and post those here. You can also email me a couple of files at support@pragmasys.com.
Pragma Systems Technical Support 13809 Research Blvd, #675 Austin, TX 78750 http://www.pragmasys.com
|
|
|
|