Loading...
 
Skip to main content

Architecture / Installation


Help : I forced the www. option without DNS. Hot to get control back

I'm in the middle of configuring my new tiki, and I was so glad I managed to get LDAP authentication working this morning, but now I get a "503 Service Unavailable" error, as I may have checked a booby-trap option forcing some prefix in the URL :

Since my server is not in the DNS yet, I use the 10.20.x.x to get to it. But now it apparently redirects to www.10.20.x.xQuestion and of course that cuts all access. Can someone tell me how to change that back to normal ?

I got some help here, but apparently to no avail as the (multiple ?) cache(s) is in the way. I'm connected by SSH/mysql on the server, but it does not seem to work.

Any help welcome.

Nice to see 6 persons (now 19, but I may be counted several times) have already read the post 😊 Still no expert with a solution ...

I connected to the server with ssh (I don't have xwindows here on my old desktop), started mysql in CLI, ans I've seen in the tiki database, table tiki_preferences the name/value pair tiki_domain_prefix/force. Modifying it in "strip" or "unchanged" would not help. But I searched all files in /var/www for "tiki_domain_prefix" and there seems to be no single occurence (correction, the search was for files, I restarted it for text in files and there _are_ hits), so that could be a wrong direction to search.

Anyone a tip ? Can I clear the cache by CLI command ?


If you have phpMyAdmin on your server or some other way to edit the Tiki installation's database directly, you can go to the tiki_preferences table and change the authentication preference, to "tiki", I believe.

-- Gary

Wow, even a response now.

Hi Gary,

Unfortunately the problem is not in the authentication. Actually I have it set on tiki+ldap, with admin and local accounts using tiki system, and creating users when they authenticate with LDAP. And that works fine. Now the problem is that you can't even access any page unregistered, the http://10.20.x.xQuestion is redirected to http://www.10.20.x.xQuestion, so that string calls DNS in turn, and obviously "www.10.20.x.x" cannot be resolved.

And on this machine, I got no phpmyadmin unfortunately. Only CLI.


Apparently, the problem was solved a while after I had the database modified manually (maybe there is an expiration of cache daily ?)