Click to Deploy Wordpress, Unable to "Allow HTTP traffic" - wordpress

I'm a new user, trying to use "Click to Deploy" for Wordpress.
The next instruction is to click on the IP address for your server and follow the instructions to Allow HTTP traffic.
However, when I go to Compute > Compute Engine > VM Instances
...when I try to click on the IP Address in the EXTERNAL IP column, it has no function.
Information from the install:
"Your Wordpress server has been deployed
Deployment information
Zone: us-central1-a
Machine Type: g1-small
Image: debian-7-wheezy-v20140926
Wordpress Version: 4.1
phpMyAdmin Installed: true
What to do next:
To open the HTTP port to your server:
Find your server in the Compute Engine Instance List
Click on the IP address for your server and follow the instructions to Allow HTTP traffic
The HTTP port will not be accessible until this step is completed
Set up Wordpress by navigating to this IP address with your browser
Access phpMyAdmin at your external IP address appended with /phpmyadmin"

I agree that the instruction provided by the Developers Console is not very accurate.
What you need to do in order to allow HTTP traffic and be able to access to your fresh instance is:
Go to Compute > Compute Engine > VM Instances > wordpress instance. This should match the following regular expression: wordpress-([a-z\d]){4}.
Click the 'Allow HTTP traffic' checkbox.
Click on the external IP address and you should be redirected to: <external IP address>/wp-admin/install.php.

Related

ERR_CONNECTION_REFUSED And Domain refused to connect

I'm trying to connect WordPress instance on google cloud with the custom domain but I'm having this error
This site can’t be reachedquotivy.com refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
What I found it wired is that the domain is working on Tor browser and not working on Chrome and Safari, and I tried to take an online screenshot from it and it's working & I ping the domain and seems working too! not so sure what to debug or do to fix this bug!
This is a sample URL: https://quotivy.com/rumi/when-the-world-pushes-you-to-your-knees/
How it looks like on my browsers:
Custome DNS on my google cloud
If you have moved the site recently then check in your database (either domain.com/phpmyadmin or SSH if Cloud SQL) for references to the old domain and update to the new domain. This includes moving from http to https
In GCP Compute Engine VM Instance settings, make sure to allow http and allow https traffic. You may want to assign a static IP in GCP Console > VPC Network > External IP addresses
Lastly you may need to update etc/apache2/sites-enabled/000-default.conf to make sure your servername matches your WordPress domain name

When I run my daemon the service is a http proxy instead off http

I am currently running a service with systemctl, and it is running as an http proxy, not normal http. Is this something that Google does? I am using port 8080 and I can't connect to it via http. My daemon is using port 8080, while using the type http-proxy (I am seeing this with the command nmap -sV -sC -p 8080 35.208.25.61 -vvvv -Pn). Instead, I want the daemon I'm running (wings.service) to use http, so it can use that type of connection to connect to my panel.
The panel is part of a piece of software along with the daemon, it's called pterodactyl. Anyways, I have tried everything on what to do, and I think this problem that I am addressing is the problem that causes dysfunction on my panel. I might just have to move to a different service to host my bots for discord.
Let me know if there's anything I can do to fix this.
As per I can understand you are unable to access the panel via web URL.
Pterodactyl web server can be installed using NGINX or Apache web servers, and both web servers by default listed on port 80 based on Pterodactyl web server installation guide, so you must enable HTTP port 80 traffic on your Compute Engine VM instance
The default firewall rules on GCP do not allow HTTP or HTTPS connections to your instances. However, it is fairly simple to add a rule that does allow them following this steps:
1.-Go to the VM instances page.
2.- Click the name of the desired instance.
3.- Click Edit button at the top of the page.
4.- Scroll down to the Firewalls section.
5.- Check the Allow HTTP or Allow HTTPS options under your desired VPC network.
6.- Click Save.
Note: The Pterodactyl panel and Daemon installation are not the same for each operating system, if after checking the VPC firewall rules on the VM settings and also the status of the web server in the instance (NGINX or Apache) you still cannot access your panel, please provide a step by step list with all commands you followed to complete the installation, including the OS version you used.

Google Cloud PHP my admin is not getting connected with ssh

I've been trying connecting my PHP my admin via ssh Client tool putty, but my URL gets redirected to my website URL from 127.0.0.1:8888/phpmyadmin to example.com:8080/phpmyadmin which throws me the following error
For security reasons, this URL is only accessible using localhost (127.0.0.1) as the hostname.
This is a built-in security feature. In order to access your server using SSH using Putty, you must create an SSH tunnel to route your request.
I found this guide that explains in detail how to get this set up:
https://docs.bitnami.com/google/faq/get-started/access-phpmyadmin/

website Hosted on Ec2 not responding, what happened with My instance?

On Friday I hosted a WordPress site on my micro instance - I installed LAMP stack, and WordPress on it.
Instance state is Running, but when I try to access website with public domain given in console, it says
web page Not available
I have set an Outbound rule to allow everyone and Inbound rule for my IP address only.
This is about accessing website from outside world, but when I try to connect to my instance with JAVA Interface, MindTerm Web SSH, it says
Network connection timeout error
Can't figure out anything, Just started working on AWS.
I think you have confused the Outbound and Inbound rules - Outbound means traffic going out from the server, while Inbound means traffic from the internet to the server.
As you say, you added an Inbound rule for your IP address only, and you can access the website from you IP only, just like you requested.
Add an Inbound rule for port 80 for0.0.0.0/0, and you should be able to access the site from other locations as well.
If you need to open it to HTTP and SSH, open it for both for 0.0.0.0/0:
Please verify your settings and permission based on this :
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html
You might also want to check your firewall, in case that is blocking the access..

How to open a website by entering its name, not the IP address of the server

I have created a website and set it up on IIS on a Windows Server 2008 R2 which is on the local network. What should I do to be able to access that website by typing its name in the browser from client machine? Right now there're only two sites: One is the Default Website and the other one is my newly created one. If I type this IP in the browser of a remote computer, which has access to the server, the default website opens. If I add https:// to the ip address I get directed to my website. This means the website opened is decided upon the protocol (http or https). What if I add another website that would require SSL?
Actually the site you browse to is not decided by the protocol, it's decided by the port. By default HTTPS is port 443, and HTTP is port 80.
So if you have an HTTPS and HTTP protocol added to a website in IIS, you've created bindings for these two ports automatically.
This is visible by going into IIS clicking "Sites" from the "Connections" section in the left pane and then looking at the "Bindings" column in the center pane.
If you create another website on the host which uses SSL you would have to assign it to a different port.
To browse to that new SSL website you would have to enter the port when browsing to it.
e.g. https://serverName:444
(You don't have to enter default ports, 80 & 443, your browser automatically infers which to use from the protocol type and adds them if no other is present)
This is inconvient for users so people get around this by registering domain names such as stackoverflow.com and pointing them to the address with the port e.g. https://stackoverflow.com:444, so users don't have to enter port numbers.
Have you added the website address to the host file which sits in the drives folder of the system32. If you add the website name against the IP in the host file you should be able to access it using the name rather than than IP address
Something like this- 10.18.20.108 test.stackoverflow.com

Resources