When I search on Google, my Site or blog URL comes out as an IP address, not a domain name. The reason is that depending on the server, hosting, site and blog settings, and also allow access to the IP address, or redirect, if there is a place to redirect to the domain address when the IP address is connected, there is also a place to redirect to the 403 page. Please note that the Gkkmon is experiencing this problem in the Amazon Lightsail instance Linx/Unix-Bitnami WordPress-Ubuntu Apache environment.
Serious issues that occur when search results are exposed as IP address URLs
If Google allows access by IP address, the URL appears in the search results as IP (not always), so there are many problems. The biggest problem arises when you have a site that has an SSL security certificate applied to it. Because a security certificate is issued only as a domain, not an IP address, Google does not matter if your site search results are domains like Https://example.com/post, but an error occurs when you get to an IP address like https://12.123.12.123/post. Since HTTPS is not matched with the domain address that the security certificate is issued to, it will link to the Privacy error page, and the user ' connection is not set to private. -The hacker may be attempting to steal information from the 12.123.12.123 (e.g., passwords, messages, credit cards, etc.), and you will see a warning message such as '-'. This is not a simple error message, but it is a security issue because the SSL security certificate has not been applied to the IP address at the time of the connection.
The aforementioned issues will greatly degrade user security and accessibility. This may be perceived as not being properly managed by the site, it is likely to be classified as a security issue or a spammy site, and understandably the SEO will be lowered and Google's search negatively affects it. Because it looks like it's not a star, it's a must-have, and there are three possible solutions.
3 Ways to solution when search results are exposed as IP address URL
The first way was to just wait and see. It may be temporarily marked as an IP, or it may be seen as a domain again if you wait. Because Google is not a local search engine, and this may be the case, if you wait, I thought that the IP address URL will be naturally cull and only domain address search results will be activated. I think now is absurd or wrong. However, it was quite passive and uncertain, and it was clear that the period was not determined, and that random sex was a strong wrong.
The second method was to redirect to Https://example.com/post when it was accessed by a Https://12.123.12.123/post URL that was exposed on Google. At first it was a way to look bad, and it was actually a way that many people use. However, when I clicked on the IP URL link before being redirection to the domain address, I was prompted to see the Privacy error page, and it was redirection when I clicked the Advanced tab to "go to unsafe page". Before seeing the error page, you might have noticed how to redirection it, but you didn't know how to search. Even knowing the method was not a fundamental solution because it is an environment where IP URL links can be exposed to Google search continuously.
The last method was to redirection a 403 or 400 error page for all connections to my fixed IP address http://12.123.12.13 and https://12.123.12.123 connection. The 403 error page is an error page that shows ' when a user requests a Web page or media that the server does not allow ', and a 400 error page is called ' Invalid request, the server did not recognize the syntax of the request '. Therefore, if you only connect to the IP address to show the 403 or 400 error page, it becomes the correct notification that the connection has not been accepted by the server, and if you wait until the search is reflected in this state, it will naturally be cull and leave only the domain address.
How to redirection the IP address URL to the 400 error page
The actual method of implementation is
/opts/bitnami/apps/wordpres/conf/httpd-prefix.conf
File, or in an SSH connection,
sudo nano/opts/bitnami/apps/wordpres/conf/httpd-prefix.conf
Use the command to put the following contents in the Httpd-prefix.conf file.
# redirection allowed
Rewriteengine On
# Rewrite all HTTP connections to HTTPS
Rewritecond% {HTTPS}! = On
Rewriterule ^/(. *) https://% {server_name}/$ 1 [R=301,L]
# Rewrite all WWW connections to Non-www
Rewritecond% {Http_host} ^ www. (.*)$ [NC]
Rewriterule ^ (. *) $ https://% 1/$ 1 [R=301,L]
# https://12.123.12.123 connection to the 400 error page Rewrite
Rewritecond% {HTTPS} = On
Rewritecond% {Http_host} ^ 12 .123.12.123
Rewriterule ^ [F]
# http://12.123.12.123 connection to the 400 error page Rewrite
Rewritecond% {HTTPS} = Off
Rewritecond% {Http_host} ^ 12 .123.12.123
Rewriterule ^ [F]
Change the 12.123.12.123 part to your actual fixed IP address. In fact, with http://12.123.12.123, it is automatically linked to https://12.123.12.123 because of the declaration that all HTTP connections are redirected to HTTPS. Because the bottom of the syntax does not have to be the enemy, but the safest and most neatly entered all the number of cases. After completion of the fix, SSH
sudo/opt/bitnami/cslscript.sh restart Apache
Enter the Apache and reboot.
When restarting Apache and testing, be sure to delete your browser's cookies and site data. In fact, even if all the settings are completely and properly redirected, the remaining cookies and site data may not be represented by the settings you changed. In the same environment, if you have correctly set up the Gkkmon
example.com, www.example.com, http://example.com/, and http://www.example.com/are
Redirect to https://example.com/,
12.123.12.123, http://12.123.12.123, https://12.123.12.123 are
will be redirected to the 400 Bad Request page.
Now we're just waiting to be reflected in Google search. It is said to be reflected in approximately two weeks.