# Strange deployment problem w/ phpmyadmin

**URL:** <https://www.ruby-forum.com/t/strange-deployment-problem-w-phpmyadmin/104314>\
**Category:** Deployment\
**Created:** [May 16, 2007, 6:18pm UTC](https://www.ruby-forum.com/t/strange-deployment-problem-w-phpmyadmin/104314 "2007-05-16T18:18:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vince](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/b5e925/32.png) [@vince](https://www.ruby-forum.com/u/vince)\
**Post date:** [May 16, 2007, 6:18pm UTC](https://www.ruby-forum.com/t/strange-deployment-problem-w-phpmyadmin/104314/1 "2007-05-16T18:18:02Z")

</div>

I’ve got a strange problem and it’s either related to phpmyadmin or my  
nginx setup. Since the primary purpose of the site is rails, I’ll go  
ahead and ask my question here…

On phpmyadmin, when i submit anything, the url changes from

[http://php.mydomain.com/](http://php.mydomain.com/) to [http://php.mydomain.com](http://php.mydomain.com)./

(notice the trailing period.) That of course, results in an error… the  
query still goes through so it’s not the end of the world, but it’s  
highly highly inconvenient. Anyone have any ideas where to look?

My stack:

Ubuntu Feisty  
PHP5  
Mongrel  
Nginx 0.4.13  
phpmyadmin 2.9.11

Thanks in advance…

-Vince

---

<div class="post-metadata">

**Author:** ![vince](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/b5e925/32.png) [@vince](https://www.ruby-forum.com/u/vince)\
**Post date:** [May 19, 2007, 11:47am UTC](https://www.ruby-forum.com/t/strange-deployment-problem-w-phpmyadmin/104314/2 "2007-05-19T11:47:25Z")

</div>

That’s just bizarre. The obvious place to look is in the  
config.inc.php file and make sure the domain is set correctly. I  
believe PMA has the option to force a domain, although normally it can  
auto-detect. Even if it’s not a config problem you might be able to  
work around it that way.

On May 16, 10:18 am, “Vince W.” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)
