Wiki Loads and Renders But Gives 404 Error

79 views
Skip to first unread message

Kevin Kleinfelter

unread,
Aug 26, 2019, 6:26:52 PM8/26/19
to tiddl...@googlegroups.com
I broke my node.js wiki. Can I get some guidance to fix it?  I suspect it using the DAV saver, but I don't know how to go about fixing that or why it started.

When I load https://external-url:443/ , the default page loads and renders, but the save icon (diskette) remains red for about 5 seconds, and then I get "syncer-browser-tiddlyweb - 18:09:46 26 8 2019 Sync error while processing '$:/StoryList': XMLHttpRequest error code: 404".

When I load http://internal-url:8084/ , the wiki loads just fine.

When I use external-url, traffic passes through an Apache HTTPS proxy for authentication.  When I use internal-url, traffic goes directly to my node.js tiddlywiki via my LAN.  I'm getting the following in my Apache log file:

[26/Aug/2019:17:54:08 -0400] "GET / HTTP/1.1" 200 2677647 "-" "Mozilla/5.0"
[26/Aug/2019:17:54:09 -0400] "GET /status HTTP/1.1" 200 397 "https://pkb.kleinfelter.org/" "Mozilla/5.0"
[26/Aug/2019:17:54:11 -0400] "OPTIONS / HTTP/1.1" 404 211 "https://pkb.kleinfelter.org/" "Mozilla/5.0"
[26/Aug/2019:17:54:14 -0400] "HEAD / HTTP/1.1" 404 348 "https://pkb.kleinfelter.org/" "Mozilla/5.0"
[26/Aug/2019:17:54:14 -0400] "GET /recipes/default/tiddlers.json HTTP/1.1" 200 12689 "https://pkb.kleinfelter.org/" "Mozilla/5.0"
[26/Aug/2019:17:54:14 -0400] "PUT /recipes/default/tiddlers/%24%3A%2FStoryList HTTP/1.1" 404 723 "https://pkb.kleinfelter.org/" "Mozilla/5.0"

It broke sometime in the last 5 days, but I don't know exactly when it broke, so I can't just un-do whatever change broke it.  It has been a long time since I upgraded my Tiddlywiki, but I have been messing with my Apache config.  It has been months since I added a plugin (long before the problem started) but I make near daily updates to content.  I tried restoring an old Apache config, but that didn't fix it.  

My vhost looks like this:
<VirtualHost *:443>
    ServerName external-host-name

    ProxyPass "/"  "http://127.0.0.1:8084/"
    ProxyPassReverse "/"  "http://127.0.0.1:8084/"
    Include cert.conf
    ProxyRequests Off
    ProxyPreserveHost on
    SSLEngine On
    SSLProxyEngine On

    <Location "/">
        AuthType Basic
        AuthName "Restricted Content"
        AuthUserFile /home/user1/sites/tw-apache/apache-passwords
        Require valid-user
    </Location>
</VirtualHost>

Suggestions?

Kevin Kleinfelter

unread,
Aug 26, 2019, 6:48:07 PM8/26/19
to TiddlyWiki
Found it. Fixed it.  I've got a bunch of vhosts with reverse proxy.  I had factored "AllowEncodedSlashes On" out of the individual vhosts into the global config.  It turns out that doing so has the effect of simply removing "AllowEncodedSlashes On".  When I put that back into the individual vhosts, it works again.
Reply all
Reply to author
Forward
0 new messages