phpMyAdmin not working Ubuntu Server

[ARC Gaming]

Hello!

I have recently installed VestaCP on a new off-site Ubuntu web server and I am unable to use phpMyAdmin. When I go to my.server.ip.addr/phpmyadmin/ I am presented with the phpMyAdmin logo and the text "Welcome to phpMyAdmin" with no login form.

I have a feeling this may have been caused by a recent update to Ubuntu Server as after doing apt-get update and apt-get upgrade on my local test machine I have come across the same issue.

Thanks for any help!

[skurudo]

Same questions:
viewtopic.php?f=14&t=10451#p38579

[ARC Gaming]

I do not think it is the same thing. The post you linked me to is about errors accessing the page. I can get onto the page just no login form itself.

screenshotShow

[skurudo]

Wow, that's something new.
Some errors in apache2 error log?

[ARC Gaming]

Here is whats in the logs. I have edited out my domain name.

/var/log/apache2/error.log

SpoilerShow

[Mon Feb 01 19:46:02.656281 2016] [suexec:notice] [pid 23014] AH01232: suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Mon Feb 01 19:46:02.689879 2016] [:notice] [pid 23015] mod_ruid2/0.9.8 enabled
[Mon Feb 01 19:46:02.692651 2016] [mpm_prefork:notice] [pid 23015] AH00163: Apache/2.4.7 (Ubuntu) mod_fcgid/2.3.9 PHP/5.5.9-1ubuntu4.14 OpenSSL/1.0.1f configured -- re$
[Mon Feb 01 19:46:02.692673 2016] [core:notice] [pid 23015] AH00094: Command line: '/usr/sbin/apache2'
[Mon Feb 01 19:46:53.225079 2016] [mpm_prefork:notice] [pid 23015] AH00169: caught SIGTERM, shutting down
[Mon Feb 01 19:46:54.214249 2016] [suexec:notice] [pid 24130] AH01232: suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Mon Feb 01 19:46:54.255784 2016] [:notice] [pid 24131] mod_ruid2/0.9.8 enabled
[Mon Feb 01 19:46:54.258753 2016] [mpm_prefork:notice] [pid 24131] AH00163: Apache/2.4.7 (Ubuntu) mod_fcgid/2.3.9 PHP/5.5.9-1ubuntu4.14 OpenSSL/1.0.1f configured -- re$
[Mon Feb 01 19:46:54.258778 2016] [core:notice] [pid 24131] AH00094: Command line: '/usr/sbin/apache2'
[Mon Feb 01 19:46:56.756080 2016] [mpm_prefork:notice] [pid 24131] AH00171: Graceful restart requested, doing restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using mydomain.co.uk. Set the 'ServerName' directive globally to suppres$
[Mon Feb 01 19:46:56.928216 2016] [:notice] [pid 24131] mod_ruid2/0.9.8 enabled
[Mon Feb 01 19:46:56.928555 2016] [mpm_prefork:notice] [pid 24131] AH00163: Apache/2.4.7 (Ubuntu) mod_fcgid/2.3.9 PHP/5.5.9-1ubuntu4.14 OpenSSL/1.0.1f configured -- re$
[Mon Feb 01 19:46:56.928569 2016] [core:notice] [pid 24131] AH00094: Command line: '/usr/sbin/apache2'
[Mon Feb 01 19:46:58.543107 2016] [mpm_prefork:notice] [pid 24131] AH00171: Graceful restart requested, doing restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using mydomain.co.uk. Set the 'ServerName' directive globally to suppres$
[Mon Feb 01 19:46:58.735862 2016] [:notice] [pid 24131] mod_ruid2/0.9.8 enabled
[Mon Feb 01 19:46:58.736188 2016] [mpm_prefork:notice] [pid 24131] AH00163: Apache/2.4.7 (Ubuntu) mod_fcgid/2.3.9 PHP/5.5.9-1ubuntu4.14 OpenSSL/1.0.1f configured -- re$
[Mon Feb 01 19:46:58.736203 2016] [core:notice] [pid 24131] AH00094: Command line: '/usr/sbin/apache2'

Weirdest thing is; this was perfectly fine one day then I think PHP updated or Ubuntu Server updated which may have broken it as I have mentioned it worked fine on a dedicated and a local server then they both started doing this issue.
This is the log from the dedicated server as it is the one I will be using in the future.

[ARC Gaming]

Update: I have just wiped the server then reinstalled Ubuntu 14.04LTS and then installed Vesta straight after but it still has this issue.

Edit: Seems to only be with Google Chrome. Just tried using FireFox and its working perfectly now. Can't believe it took me this long to think about trying a different browser. Must be something to do with my Chrome installation however I don't know what changed during the few seconds I was away from my computer.
This thread isn't needed any more since the problem doesn't seem to be phpMyAdmin or VestaCP specific.