We investigated and found that this issue occurred due to the failure of installing the v1beta1.metrics.k8s.io metric. This problem was resolved once we followed the Install Middle Tier Server documentation properly. https://docs.ifs.com/techdocs/23r1/070_remote_deploy/010_installing_fresh_system/030_preparing_server/40_middletier_server/This component should be marked as 'True' if it's working properly, as shown below:kubectl get apiservices | grep metricsv1beta1.metrics.k8s.io kube-system/metrics-server True
Thank you for your response. The issue has been resolved by following the instructions provided in the technical document titled "Installing behind a Proxy." Additionally, as you highlighted, I disabled the Ubuntu firewall and also I have executed the command source /etc/environmentto apply the proxy change.https://docs.ifs.com/techdocs/23r2/070_remote_deploy/010_installing_fresh_system/030_preparing_server/60_install_behind_proxy/Thank you for you support.
Thank you for your response. I truly appreciate your assistance.
Thank you for your response. This implies that we could likely achieve the desired outcome by renaming 'MAIL_SENDER1' in the IFS Connect mail sender configurations. Is renaming the only available option to achieve this, or are there alternative methods for configuring the mail sender?
Thank you for your prompt reply.
I appreciate your suggestion, and I will take that into consideration. Thank you for your valuable support.
I have investigated the issue with the SFTP server and determined that we need to add the "PubkeyAcceptedAlgorithms" in the sshd_config file to establish a connection with the SFTP server from the IFS Cloud application using the private key. By doing this, we won't need to enable known host authentication.PubkeyAcceptedAlgorithms ssh-rsa,rsa-sha2-512
how did you generate the known host file using the below query if you disabled password authentication on the SFTP server?java -cp \ifs-fnd-connect.jar;\jsch-0.1.55.jar ifs.fnd.connect.ftp.SftpClient -CreateKnownHosts=KNOWNHOSTS -hostname=SFTPHOST -username=USERNAME -password=PASSWORD
Have you enabled both password authentication and public key authentication on the SFTP server?
This implies that the SFTP reader requires both the known host file and the private key to be uploaded to the SFTP reader configuration to ensure its proper functionality.
Thank you for the prompt response. I can successfully connect to SFTP using the known host file from the application. However, when I attempt to use the private key-public key pair, it fails to connect to the SFTP location. Do I need to configure both the known host and the private key in the application?
I have successfully resolved the issue by modifying the SAS URL. Kindly follow the steps outlined below for your reference:1. Navigate to the Storage account and access the shared access signature under the "Security + Network" section.2. Generate the SAS URI from the aforementioned location (Allowed resource types - Service,Container,Object).3. Subsequently, obtain the Blob Service SAS URL and append your container name before "?sv," as illustrated below:https://testbistorageacc.blob.core.windows.net/containername?sv=2022-11-02&ss=bfqt&srt=sco&sp=rwdlacupiytfx&se=2025-04-01T03:25:18Z&st=2024-01-03T20:25:18Z&spr=https&sig=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx%3D4. Additionally, please ensure the accuracy of the modified SAS URL by verifying it through the Microsoft Azure Storage Explorer.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.