[davidelbert]

Well, my immediate problem is solved. The error was some strange interaction with wordpress configuration settings. The settings files had picked up the :16080 port and saved it, so the server at large was working on port 80 once the performance cache was off, but the blogs were all redirectin themselves to a port that was not functional.

I will never understand the crosstalk that made that happen, but now that it is ferreted out and fixed, things are working smoothly.

I will continue to wonder a bit about the performance cache, but it won’t keep me up nights!

Thanks for listening and offering advice. 😛

[davidelbert]

only one site, so that doesn’t seem to be the trick.

there is a cache config file at: /private/etc/webperfcache/webperfcache.config that gets changed when I toggle the cache on/off in the Site Options. Basically, it just seems to add a line at the very end that says:

WebPerfCacheListenAddress 0.0.0.0:80 16080 * “/var/log/httpd/access_log” fixed “%{PC-Remote-Adde}i %l %u %t \”%r\” %>s %b”

I guess if no one knows of another config file, or the details of this one, I will have to take it apart and try to understand it… 163 lines 😢

[davidelbert]

Actually, just turning off the cache doesn’t solve the problem. The site still tries to redirect one of my wordpress blogs that it was moving to port 16080. It seems to have left some configuration behind that I have to clear. But if I don’t know where it is, I can’t clear it.

[Author]

Posts