--On Friday, August 08, 2003 01:27:49 +0200 Jean Jordaan <[EMAIL PROTECTED]> wrote:
I can't log in to the admin account, no way - no how. I've tried the zpasswd.py command/script.
This password should get you in at http://<yourhost>:<zopeport>/manage i.e. the root of the Zope server. Now you're logged in to Zope's management interface. This is quite seperate from Plone. In this root, you probably need to add a Plone instance, let's say with the id plone. Then you should browse to http://<yourhost>:<zopeport>/plone and join the plone site there.
Nope. Doesn't work as advertised for me...
===snip===
phaedrus root # /etc/init.d/zope stop
* Stopping zope... [ ok ]
phaedrus root # cd /usr/share/zope/zope*
phaedrus zope-2.6.1 # ls
Makefile access inituser lib setup.py stupid_clean w_pcgi.py wo_pcgi.py z2.py zpasswd.py
ZServer import inst pcgi setup.pyc utilities w_pcgi.pyc wo_pcgi.pyc z2.pyc zpasswd.pyc
phaedrus zope-2.6.1 # ./zpasswd.py inituser
Username: zopeadmin
Password:
Verify password:
Please choose a format from:
SHA - SHA-1 hashed password (default) CRYPT - UNIX-style crypt password CLEARTEXT - no protection
Encoding: SHA
Domain restrictions:
phaedrus zope-2.6.1 # /etc/init.d/zope start
* Starting zope... [ ok ]
phaedrus zope-2.6.1 # nmap localhost
Starting nmap 3.30 ( http://www.insecure.org/nmap/ ) at 2003-08-07 18:05 CST Interesting ports on localhost (127.0.0.1): (The 1637 ports scanned but not shown below are in state: closed) Port State Service 22/tcp open ssh 111/tcp open sunrpc 873/tcp open rsync 971/tcp open unknown 3306/tcp open mysql 6000/tcp open X11 8080/tcp open http-proxy
Nmap run completed -- 1 IP address (1 host up) scanned in 2.089 seconds phaedrus zope-2.6.1 # ===ends===
So Zope is listening on 8080.
I fire up my browser and enter: http://localhost:8080. Gets me the start page (so I know everything is working). Then I go to http://localhost:8080/manage. Get me a login prompt. Enter the exact same username/password entered above, and it won't let me in.
Seems like this should be an easy problem to solve, but it hasn't been so far.
If it's nothing I'm missing, I'll file a bug report -- might be something amiss with the installation process. For one, the ebuild should spit out the admin username/password set by default during the install.
Best, /tom
-- [EMAIL PROTECTED] mailing list
