Error - publish over SSH shows ailed to connect SFTP - jenkins

I am trying to connect remote server to jenkins using publish over ssh.I got this error while
doing test configuration.
jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection. Message: [Failed to connect SFTP channel. Message [4: Received message is too long: 1349281116]]

Related

jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection

I am stuck to configure publish over ssh in jenkins.
Jenkins container to ansible container in CLI I am able to do SSH via private key, but the same private key when I am using on publish over ssh it does not work.
jenkins.plugins.publish_over.BapPublisherException: Failed to connect
and initialize SSH connection. Message: [Failed to connect session for
config [ansible]. Message [USERAUTH fail]]

I solved this problem yesterday morning. In the ssh configuration file I added two lines, now working perfectly.
PubkeyAuthentication yes
PubkeyAcceptedKeyTypes=+ssh-rsa

Why i get error like can't connect to server in ec2

I am unable to connect to remote ec2 host and added credentials in jenkins server using manage jenkins->configure system, during test connection. I always get error as can't connect to server.
Thanks

Connection refused trying to get account info in Solana

solana account <address>
When I get account info, I have this error:
Error: RPC request error: cluster version query failed: error sending request for url (http://localhost:8899/): error trying to connect: tcp connect error: Connection refused (os error 111)

The error is indicating that the CLI RpcClient can not communicate with the Solana validator.
This is usually caused by not having solana-test-validator running in another terminal. Many make the mistake of thinking that the localhost is running the validator all the time... it's not.
In one terminal do: solana-test-validator which will startup up the local validator
Open a second terminal and do solana account - This will return account info for the default keypair

It's a network connection problem.
I use ubuntu 20.04, I was using windscribe VPN because my location and got the error, now I'm using psiphon VPN and it's working fine.

Why fastlane upload to TestFlight fails behind proxy?

I am using fastlane to build the IPA file and trying to upload it to the test flight. I am working behind a proxy network, so exporting http_proxy and https_proxy is working fine.
You can also see from the below log, 'Login successful'. But when fastlane is trying to upload the file, getting Malformed reply from SOCKS server error.
What do you think? How do you think I can fix this error?
[13:51:26]: [32m----------------------------------
[13:51:26]: [32m--- Step: upload_to_testflight ---
[13:51:26]: [32m----------------------------------
[13:51:26]: Login to App Store Connect (****)
[13:51:29]: Login successful
[13:51:30]: [32mReady to upload new build to TestFlight (App: 1****2)...
[13:51:30]: Going to upload updated app to App Store Connect
[13:51:30]: [32mThis might take a few minutes. Please don't interrupt the script.
[13:53:46]: [31m[Transporter Error Output]: Communication error. Please use diagnostic mode to check connectivity. You need to have outbound access to TCP port 443.
[13:53:46]: [31m[Transporter Error Output]: An exception has occurred: Malformed reply from SOCKS server
[13:55:48]: [31m[Transporter Error Output]: Communication error. Please use diagnostic mode to check connectivity. You need to have outbound access to TCP port 443.
[13:55:48]: [31m[Transporter Error Output]: An exception has occurred: Malformed reply from SOCKS server

Docker setup - facing issues while running chaincode locally

I've successfully installed Docker and Hyperledge-fabric v0.6 on my local system. Unfortunately while trying to run a sample chaincode, I'm facing with the below mentioned error. Please guide me to run my chaincode successfully.
addrConn.resetTransport failed to create client transport: connection
error: desc = "transport: dial tcp [::1]:30303: connectex: No
connection could be made because the target machine actively refused
it."; Reconnecting to {"localhost:30303" } 10:05:25.048 [shim]
ERRO : Error trying to connect to local peer: grpc: timed out when
dialing Error starting Simple chaincode: Error trying to connect to
local peer: grpc: timed out when dialing
C:\Users\Arunh\goworkspace\src\github.com\testapp\learn-chaincode\start>docker-compose
op 'docker-compose' is not recognized as an internal or external
command, operable program or batch file.

Hyperledger Fabric has evolved quite a bit since the v0.6 release. Recommend if you are still on v0.6 that you upgrade to v1.0.x. http://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html

Resources