Timeout while trying to vagrant up - virtual-machine

I'm running out of ideas. I'm trying to follow the Laravel homestead tutorial to start using vagrant but I keep getting connection timeouts when I try to vagrant up..
I'm running Windows 7 on my physical host. I develop in an 64 bit Ubuntu 14.04 VM and run vagrant inside of that. I'm not sure if this sort of VM Matryoshka doll setup is causing the issue or what.
I have additionally ensured that hardware virtualization is enabled in BIOS and enabled PAE/NX on both my guest Ubuntu VM and my homestead vagrant instance.
The issue is replicatable too. It's happening on my desktop and laptop with similar configurations in the exact same way.
The error I'm seeing is as follows:
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
Timed out while waiting for the machine to boot...

To troubleshoot startup timeout problems like this, I find it useful to enable the GUI mode so you can see if it's stuck during the boot cycle. I have some more details in this answer: Vagrant up timeout
+1 for Matryoshka doll reference :)

Related

cannot connect to X.X.X.X:10514: Connection refused

Configuring a ELK stack version 8.1, based on two virtual machine which both run Oracle linux 8. I need to send logs from a VM to the other using rsyslog. On the recieving machine logs will be acquired using FileBeat. The file rsyslog.conf has been configured on the sending machine, adding target machine parameters. The file filebeat.yml has been configured to recieve logs from rsyslog like this:
- type: syslog
enabled: true
format: auto
protocol.tcp:
host: "X.X.X.X:10514"
The firewalld on the receiving machine has been configured opening the port 10514.
Since the reboot after configuration, the only thing I can get is the error:
cannot connect to X.X.X.X:10514: Connection refused
How can I solve this problem?

After installing BigBlueButton 2.3-dev, I am unable to connect via SSH. Why?

I have a VPN server (on A2Hosting) with Ubuntu 18.04 installed. The server meets the minimum configuration required for BBB. I was able to connect to this server via ssh and installed BBB 2.3-dev. It installed successfully and I can access the main page in my browser. But, after install SSH is not working. When I try to connect, it says connection timeout.
ssh: connect to host 1xx.xxx.xxx.xx7 port xxx2: Connection timed out
I have tried resetting the server, reinstall operating system and bbb several times, but whenever bbb install without error, SSH stops working. I am facing this for last couple of days. Please suggest what can be the issue.
After a lot of digging, I found that the port was blocked by firewall. My hosting provider was using non-standard ssh port 7822. Unblockimg the port solved the issue.
ufw allow 7822

Unable to start OHS component

Middleware: Oracle HTTP Server(OHS)
Version: 12.2.1.3
Configured Oracle HTTP Server(OHS) in standalone mode. Node manager is running perfectly. While starting "./startComponent.sh ohs1" i am getting the below error,
"""
javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
Error: Error occurred while performing nmConnect : Cannot connect to Node Manager. : Unrecognized SSL message, plaintext connection?
"""
The solution found in internet is to changing the SecureListener to false in Nodemanager properties file.
When i did that i got the below error,
"""
weblogic.nodemanager.NMConnectException: Connection refused (Connection refused). Could not connect to NodeManager. Check that it is running at localhost/XXX.0.X.X:XXXX.
Error: Error occurred while performing nmConnect : Cannot connect to Node Manager. : Connection refused (Connection refused). Could not connect to NodeManager. Check that it is running at localhost/XXX.0.X.X:XXXX.
"""
And the solution for this is Setting the SecureListener to true in node manager properties file.
I am confused. Can someone help in resolving these errors?
Installed Oracle Access Manager(OAM) and OHS on same machine, but installed OHS in Standalone mode in different folder. After that, uninstalled OHS and Installed OHS in the same folder where i installed OAM, It worked.

GnuTLS error -15 on vsftpd

I am using ubuntu server with vsftpd service, connecting over SSL. When connecting using Filezilla randomly getting below error.
Error: GnuTLS error -15: An unexpected TLS packet was received.
Error: GnuTLS error -15: An unexpected TLS packet was received.
Error: Failed to retrieve directory listing
It will be okay after restarting vsftpd service and will again showing after some days. tried reinstalling vsftpd service and regenerated certificate.
Here is my /etc/vsftpd.conf`
rsa_private_key_file=/etc/ssl/private/vsftpd.key
rsa_cert_file=/etc/ssl/private/vsftpd.pem
ssl_ciphers=HIGH
pasv_enable=YES
pasv_max_port=12110
pasv_min_port=12099
port_enable=YES
pasv_address=<ip>
ssl_enable=YES
allow_anon_ssl=NO
force_local_data_ssl=YES
force_local_logins_ssl=YES
ssl_tlsv1=NO
ssl_sslv2=NO
ssl_sslv3=NO
require_ssl_reuse=NO
allow_writeable_chroot=YES
pasv_promiscuous=YES
I have tried both active and passive mode and using ec2 instance and ports are opened on security groups. Tried same time different ISP ips and different location( not a local firewall issue).
Added the line seccomp_sandbox=NO on /etc/vsftpd.conf file solved my issue.

SFTP error: No connection could be made because the target machine actively refused it. (INTERMITTENT)

when we try to connect to a SFTP server we INTERMITTENTLY get the ff. error:
"No connection could be made because the target machine actively refused it".
I've been trying to search but i cannot find a similar case where this happens randomly - sometimes we can successfully connect and sometimes we encounter this error. We turned on the verbose log and this is part of what we read:
"2017-03-15 07:24:38.833 INFO SshSession(1)[8] SSH: Connecting to
sftp.igxfer.com:22 using SshSession 3.0.5885.0.
2017-03-15 07:24:39.926 ERROR SshSession(1)[8] SSH: Rebex.Net.ProxySocketException:
No connection could be made because the target machine actively refused it. --->
Rebex.Net.ProxySocketException: No connection could be made because the target
machine actively refused it.
---> System.Net.Sockets.SocketException:
No connection could be made because the target machine actively refused it 52.33.119.6:22
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)"
Any thoughts? TIA!