Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter rylan76

    (@rylan76)

    Hi all

    Managed to solve this, I had the “Really Simple SSL” plugin still active.

    Manually disabled it, now the site is partially loading at least.

    Thanks for the replies!

    Stefan

    Thread Starter rylan76

    (@rylan76)

    Hi markrh

    Thanks for replying!

    I can access the readme.html file fine and it renders in normal HTTP – no HTTPS auto-selected.

    What exactly does that mean?

    I surmise that WP itself IS still doing the HTTPS redirect, not apache or some factor outside the WP code…

    Thanks again

    Stefan

    Thread Starter rylan76

    (@rylan76)

    Hi Jarret

    Thanks for replying!

    Not sure, if I run

    apachectl -S in my Linux instance hosting the site I get pretty standard results with no mention made of HTTPS:

    # apachectl -S
    VirtualHost configuration:
    ServerRoot: “/etc/httpd”
    Main DocumentRoot: “/var/www/html”
    Main ErrorLog: “/etc/httpd/logs/error_log”
    Mutex authdigest-opaque: using_defaults
    Mutex proxy-balancer-shm: using_defaults
    Mutex rewrite-map: using_defaults
    Mutex authdigest-client: using_defaults
    Mutex proxy: using_defaults
    Mutex authn-socache: using_defaults
    Mutex default: dir=”/run/httpd/” mechanism=default
    Mutex mpm-accept: using_defaults
    PidFile: “/run/httpd/httpd.pid”
    Define: _RH_HAS_HTTPPROTOCOLOPTIONS
    Define: DUMP_VHOSTS
    Define: DUMP_RUN_CFG
    User: name=”apache” id=48
    Group: name=”apache” id=48

    The above seems to imply no VHOST-enforced redirection?

    Thread Starter rylan76

    (@rylan76)

    Also see Clayton James’ reply just above, that turned out to be exactly my problem. The sub-directory I had it in, instead of straight in /var/www/html.

    Thread Starter rylan76

    (@rylan76)

    Hi!

    Yes I managed to find a solution, but I’m not sure it is what you are looking for.

    Turns out my problem was that I placed my WordPress folder one folder too deep down the directory tree in my /var/www/html on the server.

    The site was developed by an outside company, and I wanted to place the site they developed for us in a seperate folder inside /var/www/html/ eg. I wanted to do this

    /var/www/html/the_site/index.php
    /var/www/html/the_site/wp-admin
    etc.

    and place the files in there.

    That broke my permalinks for some reason. Turned out when I placed the site here

    /var/www/html/

    and left everything as-is it started working perfectly.

    So the solution in my case was to place the entire wordpress codebase directly in

    /var/www/html/

    instead of trying to place it -anywhere- else on my Apache instance’s htdocs folder tree.

    Hope this helps.

    Regards

    Stefan

    Thread Starter rylan76

    (@rylan76)

    Hi Clayton

    Thank you very much for the detailed reply and your time taken to respond.

    Ok, my status compared to your setup (differences in which I can then only logically conclude must be the differences that are breaking permalinks and everything dependent on them):

    – I have WP installed in var/www/html/live, not /var/www/html

    – All instances of the string “AllowOverride” in my httpd.conf read “AllowOverride All” – not just one. I started at the one defining /var/www/html, and when that didn’t work turned every AllowOverride to “all” for /var/www and for / too. Also tried turning it back with “AllowOverride all” only for /var/www/html still same problem.

    – I’m not using a virtual host as well, just the one site all alone on one Apache / PHP / MySQL setup, on one Linux server, freshly installed from a Centos 7 DVD image, and fully yum updated.

    – My SELinux is disabled with “SELINUX=disabled” in /etc/selinux/config

    – I had “user:user” permissions on /var/www/html, I changed this to “username:apache” and had WP rewrite the .htaccess, no luck. Permalinks still broken.

    – I ran “httpd -M | grep rewrite” and got back “rewrite_module (shared)” so mod_rewrite is loaded and apparently running. (I’m reasonably sure it is working, if I edit .htaccess and insert something meaningless like “abc” the server crashes with a 500 internal server error, indicating it IS reading and parsing the WP .htaccess.)

    I’ve been at this now for a total of about 17 hours cumulatively (just to get permalinks working) – as regards the permissions and installation steps I’ve rehashed those over and over, reinstalled, etc. – the site keeps on working in all combinations I’ve tried, just permalinks (and some stuff apparently depending on them, like the Gravity Forms) never, ever, work – no matter what we try.

    Its approaching the point where trying to host WordPress is just becoming too expensive, and other crucial stuff is falling behind.

    We’ll probably abandon it and go back something simpler to configure and set up. If you use something like JSP pages hosted on Jetty (Java) which I’m a bit more familiar with, in 17 hours I could have probably written something that can at least do the basics we want…

    I did think WP – being so common and popular – was a good alternative choice and would save time, its incredible popularity implying it is easy to use and setup – but clearly I was totally, utterly wrong in that assessment. Using WP is probably simple (I hope…) but -hosting- it and getting it into a working state in the first place is proving a practical impossibility (at least here.)

    Anyway, thank you VERY much for your kind assistance!

    Regards

    Stefan

    Thread Starter rylan76

    (@rylan76)

    Hi Clayton

    Thx for the response. I’ve done a search of my httpd.conf and replace all lines I could find with the string AllowOverride to read AllowOverride All and restart apache.

    No luck on that, the problem remains exactly the same – any type of permalink using any tag / token, instantly takes the entire site offline and all pages just give 404 errors.

    Thx for the reply!

    Thread Starter rylan76

    (@rylan76)

    Hi t-p

    Yup, done all that, I suspect my server is (somehow) incapable of hosting WordPress.

    I’m running stock Centos 7 yum insatlled Apache and PHP instances – any idea if stock standard Centos 7 PHP and Apache are in fact capable of running Wordpres 4.7.2?

    Thx

Viewing 8 replies - 1 through 8 (of 8 total)