• I run a small garden variety Linux server with a few dozen wordpress accounts on it, all 1.5.* versions.

    Recently, I had to move servers from my own VPS to one I co-locate, so I have root on both. (New server runs CentOS4.2 w/CPanel)

    Problem: Every one of the WP installs is generating the same error as seen in the error logs from each account with a WP install. This only happened after the switch from one server to the new one.

    The feeds all work properly.
    I’ve tested the
    https://mydomain.com/feed with https://feedvalidator.org/
    and they all pass with flying colors.

    I use FeedDemon, and it picks up the feed from the footer just fine.

    Here’s the error from my error logs:
    ***
    File does not exist: /home/myacct/public_html//feed:https://mydomain.com/

    File does not exist: /home/myacct/public_html/feed:https://mydomain.com/
    ***
    (One has the single slash and one has the double slash after public_html)

    If the feeds themselves work, what application are people using (it’s a wide variety of IPs, so it’s not a ‘bot issue) to cause this error? The feeds all work, but it must be some link on every page, or some mis-configuration of the server types that causes this error.

    If this error had happened on just a single WP install, I would know it’s a configuration issue. However, this has occurred on every install across the server, and while this seems like a petty issue, I really would like to know how to fix this.

    I’m afraid I’m a bit of a newbie with things like configuring MIME types on the server, but some of my searching has pointed me in that direction.

    If this is just a case of providing a line in the .htaccess file, fine, but again, this is a server wide issue.

    Before I tackle advising everyone to upgrade to WP2.0, I’d like to have this issue solved first, lest we have the same issue with feeds (or worse) on the upgraded blogs.

    Any ideas here?

Viewing 2 replies - 1 through 2 (of 2 total)
  • I had a similar issue using 1.5 awhile back. From what I remember, check in the footer (or wherever the feed link is situated on your theme). I had to manually update the code there to remove the extra /. Alternatively, just hard code in the correct feed location. Good luck.

    Thread Starter windyt

    (@windyt)

    When you maually hit on the link in the footer, it’s configured correctly. No error gets added to the server error log for the missing file, either. The feeds as well as the feed links seen in the footer (ala the 1.5 default theme)all work.

    Plus, it’s consistant across the 20 or so WP installs on the server. The theme variations don’t seem to matter.
    I see it dozens a times per day on any domain’s error log I choose to look at. So, I’m pretty sure it’s a server issue, but I can’t create the error on my end.

    Something is making the direct server reference to the /home directory instead of a relative link. Obviously, there are no actual links on the blog page as it’s written that point to
    /home/myacct/public_html/ anything

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘feed getting redirected to /home/account//feed://mydomain’ is closed to new replies.