I am trying to install Attunity Replicate into a local virtual machine with CentOS 7 on it. I can see that it is running - using 'ps -ef | grep repctl', and I know that the 3552 port is open in the firewall, and the host is visible (using 'nc -zv 3552').
But I cannot connect my UI browser to Attunity server using 'https://:/AttunityReplicate' - the Safari answers that 'Safari can't open the page XXX becauseSafari cannot establish a secure connection to the server...', and Chrome answers with 'ERR_SSL_SERVER_CERT_BAD_FORMAT' error...
Any hints - what and where should I configure in the Attunity Server to resolve the security issue, please?
Kind regards,
Alex
On the Linux server where you installed Replicate Express, cd into /opt/Attunity/replicate/bin (this is the default location) and run the following command:
cd /opt/attunity/replicate/bin
source arep_login.sh
./repctl SETSERVERPASSWORD
./arep.ctl stop
./arep.ctl start
Ensure that your Linux server allows inbound TCP connections on port 3552
Open your browser and try to connect to the following URL: https://:3552/attunityreplicate replacing with the DNS name or IP address of the Linux Server where Replicate is installed.
When prompted, enter the Username: Admin and Password from Step 1.
You may have to allow the webpage on Chrome:
1- On your computer, open Chrome.
2- On the page where you see a warning, click Details.
3- Click Visit this unsafe site.
4- The page will load.
Reference: https://support.google.com/chrome/answer/99020?co=GENIE.Platform%3DDesktop&hl=en
Related
I am trying to connect to the Virtual Machine that I have in the university to open Jupyter Notebook and I am trying to use the localhost port 8000 to be forwarded to the VM Server but, each time I got "this site can't be reached" error and that I need to check the internet connection and firewall.
I tried a couple of things to solve the problem but nothing worked:
1- Disabling the firewall.
2- Clearing the browser history (both Chrome & Safari).
3- Resetting the settings to the default in the browser (both Chrome & Safari).
4- Changing the IP address.
Any idea how can I get this problem solved?
Thanks
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
I've setup a weblogic cluster with 2 managed servers.In order to configure node manager on both nodes i've followed the related article :
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/wls/12c/12_2_1/01-12-001-ConfiguringandUsingNodeManager/Configuring_and_Using_NM.html
with the following configuration :
Machine-0 :
DomainsFile=/u01/app/oracle/config/domains/base_domain/Machine-
0/nodemanager.domains
LogLimit=0
PropertiesVersion=12.1.3
AuthenticationEnabled=true
NodeManagerHome=/u01/app/oracle/config/domains/base_domain/Machine-0
JavaHome=/opt/jdk1.8.0_131
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=localhost
NativeVersionEnabled=true
ListenPort=5558
LogToStderr=true
SecureListener=false
LogCount=1
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=false
StartScriptEnabled=true
LogFile=/u01/app/oracle/config/domains/base_domain/Machine-
0/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
Machine-1 (the second managed server) has the same configuration with the exceptions of ports (5557) and name.
Although node manager is successfully started on both machines (startNodeManager.sh on machine-0 and machine-1) from admin console on Machine-0 the following error occurs and node manager doesnt start :
weblogic.nodemanager.NMConnectException
nodemanager.log of Machine-0 has no indications of errors or any helpful stuff.
Any help would be appreciated.
thanks in advance
These are the things that I usually check when I am setting up a new WebLogic domain:
It is possible that the Listen Address of Machine-1 is not correct. Check the Listen Address of the machine from the WebLogic Domain Configuration. It should match the host's machine name. Using localhost might not work because the Admin Server is trying to connect to the Machine-1, which can be on the other server.
Make sure to check if the port is reachable from the Admin Server's machine.
Check that the Node Manager configuration uses Plain instead of SSL connection, as stated in your nodemanager.properties file. Under Environments > Machines, click the machine and go to Configuration Tab, Node Manager. Check if the Type is Plain and not SSL. Changing this will require a restart of the Admin Server.
Please verify the items below before you start nodemanager.
Check if the nodemanager.domains has your domain name listed.
Try to see if the ports are listening using the commands below.
netstat -an|grep 5557
netstat -an|grep 5558
Also, check if the nodemanager is reachable in weblogic console.
I have successfully installed Apache Solr using terminal on the remote server (Ubuntu 14.04 on Windows Azure Servers). The status of Solr when checked using Terminal is listening on Port 8983 Happy Searching. But when I open http://MyIPAddress:8983/solr the connections gets timed out. Am I missing something here.
Have you opened the port? By default only port 22 is open for SSH and the other ports are closed by a firewall.
To open ports, go to the Windows Azure management console. Click on "Virtual Machines" choose your VM, and click on "Endpoints" at the top. Click on "Add Endpoint", and fill in the details: protocol (TCP/UDP), public port (8983), and private port (8983).
Does anyone know why I am unable to connect to my server using the Notepad++ NppFTP plugin with SFTP?
I have a CentOS 6.4 server with SSH on port 22.
When I try and connect using NppFTP I get the following output:
[NppFTP] Everything initialized
Connecting
[SFTP] Connection failed : Error reading socket
Unable to connect
Disconnected
This used to work when I had my SSH port set to 3264 but when I changed the SSH port back to 22 NppFTP stopped working. All the settings for the profile are correct including the right IP, username, password and port (22).
I can connect with SFTP using FileZilla and WinSCP successfully with these same SFTP details and I can connect with SSH using PuTTY.
I can connect with SFTP to other servers using NppFTP so I believe there is an issue in my server config I'm just not sure where or what.
I looked at the access logs but found no attempt at a connection from NppFTP, I turned the firewall off and still nothing.
In the end I got in touch with my server company and it turns out it was a problem on their end. This is what they had to say:
"This was caused by an IPS rule inspecting the network packets coming into the infrastructure, which helps identify brute force attacks."
Very strange, but after they made the change NppFTP can now connect successfully.