Unable to login to a new OPML server with Radio2

[John Evdemon]

I recently set up a new OPML server with Radio2.  I was able to verify everything is working properly on the server itself.

 

When I browse to Radio2 at http://opml.evdemon.org:5337/radio2 I get the signin page.  I login with admin and the password I defined but the signin page keeps coming up. 

 

Has anyone else experienced this issue?  Thanks in advance for any guidance or advice.

 

John

[Dave Winer]

In members.root, open up the default table, and check out the value of cookieDomain.

Make sure it has the value of the domain you want to use to access the server.

It determines what domain the cookie that the server returns applies to.

It's probably not what you want it to be. ;-)

Dave

--
You received this message because you are subscribed to the Google Groups "frontier-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to frontier-use...@googlegroups.com.
Visit this group at http://groups.google.com/group/frontier-user.
For more options, visit https://groups.google.com/groups/opt_out.

[Rich Brown]

Yes, I can confirm this is a fix. Here was my situation:

I wanted to set up a river of news on a (Mac) server at my home that was always on, and thus continually fetching news. I installed OPML as described, and it worked great as long as I went to http://localhost:5335. 

I wanted to set it up so that I could use it from other computers at home using its (NAT) IP address, without exposing it to the Internet at large. I had to do the following:

Configure the OPML Server:

1) Install OPML Editor as described in the documentation.

2) Go to http://localhost:5335/ using a web browser on the same machine where OPML runs.

3) Configure an administrator password (Prefs > Admin password)

4) Install river2 (Tools -> and click the blue "Install" on the "river2" row)

Configure the default cookieDomain:

1) In the OPML application itself, choose Window -> members.root

2) Double-click the "default" row to expand it

3) Find the "cookieDomain" entry, and change it to your local computer's IP address.

I don't know if it's necessary to quit and restart OPML, but it couldn't hurt. You should then be able to connect to your server as http://192.168.x.x:5335/river2/ (using whatever the OPML Editor machine's IP address)

Here's what I think is going on: 

- The cookieDomain of the OPML Editor supplies the "domain name" that the browser uses to return cookies set during the login process.

- The OPML Editor cleverly sets the cookieDomain to my external (non-NAT) address automatically, which is a useful default.

- However, this will never match my 192.168.x.x (NAT) address, so I had to set cookieDomain manually in the OPML Editor.

- The Prefs -> External Name web page can set the cookieDomain, but it does not accept a plain IP address

A request: Could the Prefs->External Name web page allow an IP address? That would avoid having to edit it in OPML Editor. Many thanks.

Rich Brow