• After setup the fiewall (Redirect 443 to 8443) to connect to our wordpress server, it shows “The site can’t be reached” found in Google. Please advise. Thanks.

    The https://210.177.52.161 is work with testing page displayed.

    The ssl_error_log shows the errors below.

    [Wed Aug 14 16:50:52.664044 2024] [autoindex:error] [pid 5286:tid 139674140010240] [client 59.188.133.250:58550] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php,index.php) found, and server-generated directory index forbidden by Options directive

    • This topic was modified 3 months, 2 weeks ago by aydenise.
    • This topic was modified 3 months, 2 weeks ago by aydenise.

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 15 total)
  • The IP address does not have a valid SSL certificate. Therefore, no software that is concerned about security – such as the Google Bot – will load it.

    The solution would be to get a domain and a valid SSL certificate for it.

    Thread Starter aydenise

    (@aydenise)

    Thank you for your advice.

    We found that we can acccess https://210.177.52.161/wordpress/wp-login.php but not https://210.177.52.161/wordpress/index.php. Is it due to rewrite rules problem or the problem arised from index.php ? Thanks.

    I cannot access either of the two URLs because a valid SSL certificate is missing. Since the SSL certificate has to be set up on the server system, it is in front of WordPress and no WordPress file can influence this in any way.

    Without https I get no response from the server.

    The method described above would solve the problem.

    Thread Starter aydenise

    (@aydenise)

    I have renewed the SSL cert but the same problem found. We can acccess https://210.177.52.161/wordpress/wp-login.php but not https://210.177.52.161/wordpress/index.php.

    I still can’t access it. The message is:

    Secure communication with the remote peer is not possible: Requested domain name does not match the server’s certificate.

    An IP cannot have an SSL certificate that is accepted by browsers. And the domain stored in the certificate leads me to a completely different IP address.

    Thread Starter aydenise

    (@aydenise)

    I have added the DNS for my site.

    Would you please try https://wptest.tradelink.com.hk/wordpress/index.php and https://wptest.tradelink.com.hk/wordpress/wp-login.php ? The first one is not work but the second one is work.

    In your first link, you visually wrote a different URL than the one you linked to. The linked URL contains port 8443, which is obviously not open in your system. This is also rather unusual.

    With the 2nd link, WordPress does open, but very slowly as it has obviously set a local IP (192.168.62.107) as the siteurl and home. You would have to set the public domain you have now set up as siteurl and home in WordPress.

    Thread Starter aydenise

    (@aydenise)

    Thank you for your advice.

    After I have changed the siteurl and home to public domain, it cannot allow me to access the siteurl and home page. Would you please advise ? Thanks.

    Unfortunately, I don’t know what exactly you mean by “it cannot allow me to access”. When I call up the page at the moment, I get an error 500, the cause of which you should be able to see in the error log.

    Thread Starter aydenise

    (@aydenise)

    We installed the WP in our server instead of web hosting. We have open the incoming network access from Internet to our server and is it necessary to open the outgoing network access to Internet ?

    When I access https://wptest.tradelink.com.hk, “The connection has timed out” error found.

    • This reply was modified 3 months, 1 week ago by aydenise.
    Thread Starter aydenise

    (@aydenise)

    My home and siteurl setting is shown as below.

    +————-+————————————–+
    | option_name | option_value |
    +————-+————————————–+
    | home | https://wptest.tradelink.com.hk:8443 |
    | siteurl | https://wptest.tradelink.com.hk:8080 |
    +————-+————————————–+

    Yes, because WordPress also needs to talk to its own repository to get information about updates. Depending on what else should be running on the website, there may also be other reasons to enable an external connection.

    Thread Starter aydenise

    (@aydenise)

    Would you please advise whether the url of home and siteurl have different ports will affect the case?

    As long as both ports are accessible from outside and inside, you can do this. This depends on your network configuration.

    Thread Starter aydenise

    (@aydenise)

    We have enabled the outbound connection to Internet but it still fails to display the front page using URL (https://wptest.tradelink.com.hk) but can display (https://210.177.52.161).

    In /var/log/httpd, it shows the errors below

    [Mon Aug 19 15:54:33.152396 2024] [core:error] [pid 9775:tid 140615006250752] [client 192.168.177.29:51381] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use ‘LogLevel debug’ to get a backtrace., referer: https://210.177.52.161/

    [Mon Aug 19 15:57:38.713427 2024] [core:error] [pid 9775:tid 140614913931008] [client 89.252.190.72:53242] AH00126: Invalid URI in request POST /cgi-bin/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/bin/sh HTTP/1.1

Viewing 15 replies - 1 through 15 (of 15 total)
  • You must be logged in to reply to this topic.