Our PF instance doesn't work with FQDNs

[Leif Neve]

Recently we launched our own instance of person finder and found that it doesn't work at it's fully qualified domain name (FQDN).
What we're finding is that this URL works:

  http://plpf:8000/

but this URL does not:

  http://plpf.nlm.nih.gov:8000/   (returns '404')

Using an IP address in the URL doesn't work either:

  http://130.14.37.162:8000/     (returns '404')

What's the trick to getting FQDNs to work? Thanks.

P.S. As you can see above, we turned off the requirement for SSL access.

[Leif Neve]

I should add that it's just the interactive website that doesn't work at its FQDN. The data API (i.e. feeds) works fine.

[Ka-Ping Yee]

On Fri, Sep 14, 2012 at 4:25 AM, personfinder on behalf of Leif Neve <personfinder+noreply-APn2wQeqoub...@googlegroups.com> wrote:

I should add that it's just the interactive website that doesn't work at its FQDN. The data API (i.e. feeds) works fine.

On Friday, September 14, 2012 6:47:10 AM UTC-4, Leif Neve wrote:

Recently we launched our own instance of person finder and found that it doesn't work at it's fully qualified domain name (FQDN).
What we're finding is that this URL works:

  http://plpf:8000/

but this URL does not:

  http://plpf.nlm.nih.gov:8000/   (returns '404')

Using an IP address in the URL doesn't work either:

  http://130.14.37.162:8000/     (returns '404')

What's the trick to getting FQDNs to work? Thanks.

How are you running the server?  If you are using dev_appserver.py, try setting the --address option.  Does that help?

—Ping

[Leif Neve]

Yes, we are running dev_appserver.py. We normally set this in the options: address=0.0.0.0. I just now tried
setting it to the FQDN of our instance and that doesn't help.

On Friday, September 14, 2012 6:47:10 AM UTC-4, Leif Neve wrote: