I am trying to do the following:
I have several BIRT reports that are running via Tomcat and connect to a Mysql database. However I am setting up a website on Kinsta and they do not allow to bind an external IP address (the one that is running tomcat) to the mysql database. They told me to setup a SSH tunnel. I am not familiar with this. Is this possible? To setup an SSH tunnel so that a connection can be made from the Tomcat BIRT app. If so can someone point me to a solution/explanation how to achieve this. The BIRT reports run over port 8443.
Thanx in advance
Related
I have a website that is running in Oracle Cloud, the website now is down and I tried to access using SSH in Putty but it cannot be accessed I only see the terminal screen.
What should I do?
Could you please check if the instance is running or not. If the instance is running please check for the ingress/egress firewall rules at security list/NSG/OS firewall for connectivity to the instance. Make sure you are not connected to any VPN or any corporate network. Once you are able to connect to the instance check for the status of the service. It should be Active.
Could you please confirm, were you able to connect to the instance before? Since when you are facing this issue?
For your reference: connecting to your instance.
I'm hosting Odoo on AWS and need to connect from my local machine. I am using AWS Certificate Manager instead of using a local .pem file ( no SSL configuration done on Apache as I am using AWS CM).
My odoo application works well, If I type https://myodoosite.com it works well.
What I need is to connect to the Postgresql DB on myodoosite.com
I can connect to the Postgresql DB from within the myodoosite.com server by uisng the command $psql -U postgres odoo_prod
Does anyone have an idea how to achieve this?
WHen I connect from my local, it says " Is the server running at myodoosite.com accepting TCP/IP connections on port 5432? "
Thank you for your replies.
Did I understand correctly your situation:
Odoo, Apache and PostgreSQL in one or multiple EC2 instances in AWS.
Load Balancer with SSL termination (using certificate from Certificate Manager) that exposes only your Odoo/Apache http service.
You probably have firewall rules in security groups preventing the PostgreSQL traffic in tcp port 5432. You need to open port 5432 to be accessible from your onpremise IP-address. You can do this by enabling the predefined PostgreSQL type in PostgreSQL EC2 instance's Security Group and set your IP address in the source address. Please note that this way the database is accessible for all traffic coming from that IP or IP range. So if you use shared IP this could be a problem.
Another easy and secure way to connect to PostgreSQL is to tunnel the traffic from your workstation with ssh. This is usable if you already have ssh port open and you do not want to open PostgreSQL port to public internet.
I have successfully installed Apache Guacamole on my DigitalOcean VPS.
Now I need to create a new connection to my windows 10 pc.
I cannot get that to work.
I am very confused what settings I need to fill in to connect to the pc.
Here are screenshots of the settings I can fill in. I am going to use RDP and am unsure how to find the domain, host, etc of my pc. Maybe there is other settings I need to fill in too?
Please help as I have been trying for weeks. Thank You.
New Connection Settings Picture
New Connection Settings Picture
First, make sure that both tomcat and guacd services are running. Usually, both are installed on the same machine.
On the settings page, select RDP as the protocol (in the images you have posted, VNC is selected). Next, in the "Parameters" section, enter hostname ip and RDP port (3389 is the default). If guacd is on the same host as tomcat, there is no need to enter anything in the "Guacamole proxy parameter" section.
The settings page is a bit different when RDP is selected, but you should also populate windows username, password and domain of the remote PC where you want to connect. The parameters are the same as the one you are normally using to logon to this PC.
Also, make sure that the remote windows 10 PC is accessible from the DigitalOcean VPS. You may test this by logging to the VPS machine and issue the following in the terminal
telnet <remote windows pc ip> 3389
If you can connect with telnet, this means that remote PC RDP server is accessible; otherwise, you have to check for network related issues (firewall, different lans...).
If everything above is ok, then please post the tomcat log (catalina.out) and guacd log (usually in /var/log/syslog).
I have recently launched the Bitnami Wildfly on Google Compute Engine. I have done all the configuration and everythings is working fine except for the management interface which give an error message:
The management interface could not be loaded.
Authentication required.
I know i have to create a tunnel via SSH with Putty, I did that and I am able to access the server terminal. The Tunnel i created is to allow connections via localhost:9999 from the remote port 9990.
I have also tried editing standalone.xml and changed the interface to accept connection on , that too did not work.
Kindly assist.
Solved: It appears that when configuring the tunnel use 127.0.0.1:9990 instead of localhost:9990, I guess this is because the standalone.xml is configured to accept connections on 127.0.0.1.
I am able to access an application on glassfish server locally via http://localhost:8080/domain1 or http://<machine-ip>:8080/domain1. However, I am unable to access it from another remote machine.
When I put http://<machine-ip>:8080/domain1 in a browser, connection timed out.
Firewall is off on both machines and I have also add machine-ip to /etc/hosts file. I can ping glassfish server machine I am using redhat enterprise 6.3 linux on which glassfish is installed.
Please tell how to access it via IP. DO we need to change any configuration file?
Any help would be really appreciated.
Thanks
-Sam
This might be a problem because of Selinux policy being in enforcing mode.
Try changing it to passive or disabled mode and then try accessing your server.