I use google cloud services and specially VM instance to host my web-sites,
I used to KloxoMR, and usually I install it on a fresh Centos 6 or 7 with no problem. About google cloud VM I have no problem in installing Kloxo too, but I cant access to my kloxo control panel using http://ExternalIP:7778 or 7777(https) it seems there is a problem with this two systems.
Any idea how to fix it?
You need setup firewall rules on Google Clould account
http add 7778 port
https add 7777 port
Example:
default-allow-http
Entrada
http-server
Intervalos de IP: 0.0.0.0/0
tcp:80,7778
Permitir
1000
default-allow-https
Entrada
https-server
Intervalos de IP: 0.0.0.0/0
tcp:443,7777
Permitir
1000
Related
I am in the process of deploying my MERN app to a Digital Ocean droplet(Ubuntu 20.04 server).
I have cloned my GitHub repo, installed the dependencies and pm2.
I start the server using the command pm2 start server/index.js.
Then when I visit the URL http://134.122.112.22:5000, I get the following error:
Why am I not able to access my site?
*Note that I have not yet bought a domain. Also I have not yet installed NGINX.
Am I missing something?
EDIT-1
I added a HTTP inbound rule in the firewall. Yet, I am receiving the same error.
You are missing the Nginx. Port 80 is open but you are trying 5000, so won't work.
You can open port 5000 in the firewall and also check ufw firewall.
ufw status
and open the port using command
sudo ufw allow 5000
I'd like to know in detail how to connect google compute engine virtual machine instance and app engine.
I've set up a virtual machine instance on Google compute engine, and my Postgres server is running there, following this tutorial: https://cloud.google.com/community/tutorials/setting-up-postgres
I've deployed my flask app under the same project on Google Cloud Platform, creating an app engine instance.
I searched on how to connect compute engine and app engine together, and it seems it should be possible through a VPC connector: connect Google App Engine and Google Compute Engine
This is what my VPC connector looks like:
Serverless VPC access
Name Network Region IP address range Min. throughput Max. throughput
connector-name default europe-west2 10.8.0.0/28 200 300
On my compute engine, I have my VM instance like so:
Name Zone Internal IP External IP
some-name europe-west2-c 10.154.0.2 (nic0) 34.89.113.193
On my flask app, I'm trying to connect to my remote DB like so:
db = PostgresqlExtDatabase(
"some-name", # databse name
user="postgres",
password="some-password",
host="10.154.0.2", # remote host internal ip
port=5432,
)
db.connect()
This is my app.yaml for the vpc access part, I've followed this reference: https://cloud.google.com/appengine/docs/standard/python/connecting-vpc#configuring
vpc_access_connector:
name: projects/some-name/locations/europe-west2/connectors/connector-name
If I understood correctly, if the VPC connector is present, I should just be able to connect using the internal IP address of my VM instance(this case, 10.154.0.2)?
The problem is, when the app is deployed for production, It is still complaining that it cannot connect:
2020-09-26 12:54:51 default[20200926t134815] Is the server running on host "10.154.0.2" and accepting
2020-09-26 12:54:51 default[20200926t134815] TCP/IP connections on port 5432?
If it's connected internally I assume I don't have to add that internal IP to firewall rules, although I did try that as well. As for firewall rules, I have allowed my local machine's IP address so I can connect to the remote Postgres server via PgAdmin.
I've actually tried External IP(34.89.113.193) as well although that doesn't make sense to me.
I'm a bit of a noob on networks and backend stuff in general, any help would be much appreciated.
UPDATED 1
This is my firewall rules:
Direction
Ingress, Egress
Action on match
Allow
Source filters
IP ranges
92.40.176.9/32
78.146.103.141/32
10.154.0.2
Protocols and ports
tcp:5432
Image for reference: Screenshot for the list of firewall rules
It turns out the firewall / postgres configurations were all ok, but because this VPC connector method was on beta, I needed to run:
gcloud beta app deploy
instead of the usual
gcloud app deploy.
This command then updated gcloud Beta Commands and prompted me to enable API:
API [appengine.googleapis.com] not enabled on project [742932836941]. Would you like to enable and retry (this will take a few minutes)? (y/N)?
After enabling this everything worked fine.
Per the information provided seems like both VPC firewall rules and the connector are well configured.
However, based on the messages
2020-09-26 12:54:51 default[20200926t134815] Is the server running on host "10.154.0.2" and accepting
2020-09-26 12:54:51 default[20200926t134815] TCP/IP connections on port 5432?
Seems like the VM or server using 10.154.0.2 is not accepting requests on port 5432 or the port has not been opened, you can use this site to do a port scan.
Based on the guide you followed to create PostgreSQL you are using Ubuntu as OS, therefore I suggest you open the port in ubuntu and see if the issue persists.
My website cannot go live!
The following is my web server setup.
1. Rogers modem – Hitron CODA-4582
2. Port Forwarding
Application Name Public Private Protocol Local IP Address
HTTP 80 – 80 800 – 800 TCP 192.168.0.201
HTTPS 443 – 443 883 – 883 TCP 192.168.0.201
3. Operating System - ubuntu 16.0.4
Apache2 Sever /etc/apache2.conf file.
I modified two things.
a. Uncommented the line ServerRoot “/etc/apache2”
b. Appended one line at the end of the file: ServerName my_rogers_IP_address.
I executed a command: sudo app info “Apache Full”
The output is
Profile: Apache Full
Title: Web Server (HTTP,HTTPS)
Description: Apache v2 is the next generation of the omnipresent Apache web
server.
Ports:
80,443/tcp
Then, I executed another command: sudo ufw allow in “Apache Full”
I thought I have done what I needed to do. So, I opened up the browser for testing. It only works for 127.0.0.1 or localhost. It won’t work if I enter http://my_rogers_IP_address.
Can someone give me a pointer?
Thank you in advance!
You need to point the apacheserver to a host that can actually host your website. Localhost is just a local loop between your computer's machine and the server. I would recommend using Heroku, or Cloud9, which is free. Additionally, you could buy a static IP for your site to use, however, this is not cost-effective. It is up to you whether you have the funds or just want to do this for fun.
I got my problem solved!!
It is my bad! Everything is fine except the private port setting.
The private port must be within the public port range.
Everything is working fine now. Hope this can help someone else.
Good day!
I am trying to run and OpenLDAP container on Bluemix using IBM Containers. I am using cloudesire/openldap and sucessfully run the contianer on my local linux machine. I tried to run in my Bluemix account using IBM Container.
I am unable to test it using ldapsearch or telnet using port 389. I managed to run some other container and telnet them sucessfully, but not with Open LDAP container.
Is port 389 blocked by the Bluemix router? How proxy the port?
Port 389 is currently blocked for IBM Containers running on Bluemix.
Please open a support ticket with IBM Bluemix Support and request this port to be exposed:
https://developer.ibm.com/bluemix/support/#support
I'm having trouble completing a web deploy from VS2013 as I posted in VS to Azure Publish failure: Socket Error 10054
Apparently web deploy uses port 8172, which I cannot telnet to at the moment despite rules being present in my windows firewall allowing the port through.
I am using the commands telnet localhost 8172 and telnet 192.168.0.1 8172 and it says it cannot connect to the host on port 8172.
I'm not sure this is the issue because I can complete a web deploy to Azure in my other projects? But in any event I'm confused as to why I cannot telnet to the port.
Is my syntax wrong?
JK
If you're using Azure you need to open up a port in the 'Network group' settings.
If you're using CloudFlare or some other kind of proxy, make sure to connect with the IP address of the VM or the MS supplied domain name and not your 'website domain name'. CloudFlare won't proxy through any old random port.