PHPMyAdmin fails after using ' Redirect "/" ' rule (LAMP/Wordpress)

SvenS 2017-03-01 16:06:35 UTC #1

Hi,

I have used the apache redirect rule to rederect everything to HTTPS. In the file

/opt/bitnami/apache2/conf/bitnami/bitnami.conf

I have therefore added:

Redirect "/" "https://my-domain.com/"

like this:

# Default Virtual Host configuration.

<IfVersion < 2.3 >
  NameVirtualHost *:80
  NameVirtualHost *:443
</IfVersion>

<VirtualHost _default_:80>
  ServerName 11.22.333.444
  ServerAlias www.my-domain.com my-domain.com
  Redirect "/" "https://my-domain.com/"
  DocumentRoot "/opt/bitnami/apps/abc/htdocs"
#  RewriteEngine On
#  RewriteCond %{HTTPS} !=on
#  RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]
  <Directory "/opt/bitnami/apps/abc/htdocs">
    Options Indexes FollowSymLinks
    AllowOverride All
     <IfVersion < 2.3 >
       Order allow,deny
       Allow from all
     </IfVersion>
     <IfVersion >= 2.3 >
       Require all granted
     </IfVersion>
 </Directory>

  # Error Documents
  ErrorDocument 503 /503.html

  # Bitnami applications installed with a prefix URL (default)
  Include "/opt/bitnami/apache2/conf/bitnami/bitnami-apps-prefix.conf"
</VirtualHost>

Unfortunately now the

http://127.0.0.1:8888/phpmyadmin

does not work anymore. So I have tried this:

like this:

# Default Virtual Host configuration.
    
    <IfVersion < 2.3 >
      NameVirtualHost *:80
      NameVirtualHost *:443
    </IfVersion>
    
    <VirtualHost _default_:80>
      ServerName 11.22.333.444
      ServerAlias www.my-domain.com my-domain.com
      RewriteCond %{HTTP_HOST} !=127.0.0.1
      Redirect "/" "https://my-domain.com/"
      DocumentRoot "/opt/bitnami/apps/abc/htdocs"
      ...

But that didn't help any. What can I do to access phpmyadmin again - if possible without changing the

Redirect "/" "https://my-domain.com/"

rule?
Many thanks.

davidg 2017-03-02 09:34:58 UTC #2

Hello @SvenS,

Take into account that now your content is served using the port 443, so instead of using this command:

 ssh -i [your-private-key].pem  -N -L 8888:127.0.0.1:80 bitnami@YOUR-IP

you should use this one:

ssh -i [your-private-key].pem  -N -L 8888:127.0.0.1:443 bitnami@YOUR-IP

I hope it helps

SvenS 2017-03-02 11:43:17 UTC #3

many thanks for your answer. I just change my putty configuration to
L8888 localhost:443 and
L8888 127.0.0.1:443

and connected to my VM with each of them.

Then I tried using

http://127.0.0.1:8888/phpmyadmin

but it still does not work. It gets redirected to

https://my-domain.com/phpmyadmin

and says 404 Not found.

So I guess this was not the answer I need.

Any further help is very welcome.

davidg 2017-03-03 11:40:38 UTC #4

That Apache logic is applied when accessing to port 80. Could you try accessing https://127.0.0.1:8888/phpmyadmin instead of http://127.0.0.1:8888/phpmyadmin?

Regards

SvenS 2017-03-03 22:59:56 UTC #5

Hi davidg,

thanks very much. That helped. Firefox was moaning that the page would not be correctly configured and therefore would not allow me to use the site. But after adding an exception rule to firefox it would show me the log-in page of phpmyadmin again.

Thank you!

davidg 2017-03-06 09:37:42 UTC #6

I'm glad you solved the issue. Thanks for letting us know.

Regards

SvenS 2017-03-09 13:41:27 UTC #7

sorry but I have to reopen this thread again. Currently I'm having trubble again to visite

https://127.0.0.1:8888/phpmyadmin

The error I get is SSL_ERROR_RX_RECORD_TOO_LONG

I have googled this issue in the last days but I am lost. Could it be that the SSL certificate is wrong? How would I check and repair that? Or is it my bitnami.conf file wrong?

# Default Virtual Host configuration.

<IfVersion < 2.3 >
  NameVirtualHost *:80
  NameVirtualHost *:443
</IfVersion>

<VirtualHost _default_:80>
  ServerName 11.22.333.444
  ServerAlias www.my-domain.com my-domain.com
  Redirect permanent "/" "https://my-domain.com/"
  DocumentRoot "/opt/bitnami/apps/abc/htdocs"
#  RewriteEngine On
#  RewriteCond %{HTTP_HOST} !=127.0.0.1
#  RewriteCond %{HTTPS} !=on
#  RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]
  <Directory "/opt/bitnami/apps/abc/htdocs">
    Options Indexes FollowSymLinks
    AllowOverride All
    <IfVersion < 2.3 >
      Order allow,deny
      Allow from all
    </IfVersion>
    <IfVersion >= 2.3 >
      Require all granted
    </IfVersion>
  </Directory>

  # Error Documents
  ErrorDocument 503 /503.html

  # Bitnami applications installed with a prefix URL (default)
  Include "/opt/bitnami/apache2/conf/bitnami/bitnami-apps-prefix.conf"
</VirtualHost>

# Default SSL Virtual Host configuration.

<IfModule !ssl_module>
  LoadModule ssl_module modules/mod_ssl.so
</IfModule>

Listen 443
SSLProtocol all -SSLv2 -SSLv3
SSLHonorCipherOrder on
SSLCipherSuite "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS !EDH $
SSLPassPhraseDialog  builtin
SSLSessionCache "shmcb:/opt/bitnami/apache2/logs/ssl_scache(512000)"
SSLSessionCacheTimeout  300

<VirtualHost _default_:443>
  DocumentRoot "/opt/bitnami/apps/abc/htdocs"
  SSLEngine on
SSLCertificateFile "/etc/letsencrypt/live/my-domain.com/fullchain.pem"
SSLCertificateKeyFile "/etc/letsencrypt/live/my-domain.com/privkey.pem"
# SSLCertificateChainFile "/opt/bitnami/apache2/conf/1_root_bundle.crt"

  <Directory "/opt/bitnami/apache2/htdocs">
    Options Indexes FollowSymLinks
    AllowOverride All
    <IfVersion < 2.3 >
      Order allow,deny
      Allow from all
    </IfVersion>
    <IfVersion >= 2.3 >
      Require all granted
    </IfVersion>
  </Directory>

  # Error Documents
  ErrorDocument 503 /503.html

  # Bitnami applications installed with a prefix URL (default)
  Include "/opt/bitnami/apache2/conf/bitnami/bitnami-apps-prefix.conf"
</VirtualHost>

# Bitnami applications that uses virtual host configuration
Include "/opt/bitnami/apache2/conf/bitnami/bitnami-apps-vhosts.conf"

How and where would I enable an error log that would tell me more about this issue?

Thanks for any further help.

davidg 2017-03-10 12:05:27 UTC #8

Hello @SvenS,

The error occurs in case the port a client is trying to connect to is opened on the server, but there is no certificate configured properly on the server’s side for this port.

Have you applied any change since last time which could produce the issue? Does it only happens when accessing phpmyadmin?

SvenS 2017-03-10 12:54:05 UTC #9

I am not aware of any changes since last time. Maybe I tried to reniew the SSL certificate in the meantime (but I don't know if or what really happend) and I played around with the path to the SSL certificates in the above conf-file.

Yes all the rest of the domain is fine, I just still need to change some of the links on the homepage from http to https to get the green lock without the yellow warning sign. But I don't think this has something to do with this issue.
The problem only occurs with myphpadmin. When connecting to the VM in order to access myphpadmin I think (hope!) now all the settings in my putty are correct. In the event-log it tells me:

2017-03-10 13:41:19    Looking up host "11.22.333.444"
2017-03-10 13:41:19    Connecting to 11.22.333.444 port 22
[...]
2017-03-10 13:41:20    Local port 8888 forwarding to 127.0.0.1:443

That looks good to me.

How can I "look inside" the certificat to see if it is configured correct?

When building a new certificate will I have to add all the alternatives to the certificate?

https://11.22.333.444
https://my-domain.com
https://www.my-domain.com
http://11.22.333.444
http://my-domain.com
http://www.my-domain.com

Many thanks for your help.

SvenS 2017-03-10 15:20:26 UTC #10

and in addition to that do I have to add

https://127.0.0.1:8888/

for phpmyadmin into the certificate as well?

SvenS 2017-03-13 11:31:12 UTC #11

I did some more research on my issue. I figured out that I can not issue a certificate for localhost or 127.0.0.1 or 127.0.0.1:8888 or localhost or localhost:8888.
It would give me this error:

[...]
2017-03-13 10:16:43,802:DEBUG:certbot.main:Exiting abnormally:
Traceback (most recent call last):
  File "/root/.local/share/letsencrypt/bin/letsencrypt", line 11, in <module>
    sys.exit(main())
  File "/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/certbot/main.py", line 896, in main
    return config.func(config, plugins)
  File "/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/certbot/main.py", line 692, in certonly
    lineage = _get_and_save_cert(le_client, config, domains, certname, lineage)
  File "/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/certbot/main.py", line 87, in _get_and_save_cert
    renewal.renew_cert(config, domains, le_client, lineage)
  File "/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/certbot/renewal.py", line 296, in renew_cert
    new_certr, new_chain, new_key, _ = le_client.obtain_certificate(domains)
  File "/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/certbot/client.py", line 265, in obtain_certificate
    self.config.allow_subset_of_names)
  File "/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/certbot/auth_handler.py", line 67, in get_authorizations
    domain, self.account.regr.new_authzr_uri)
  File "/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/acme/client.py", line 228, in request_domain_challenges
    typ=messages.IDENTIFIER_FQDN, value=domain), new_authzr_uri)
  File "/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/acme/client.py", line 208, in request_challenges
    new_authz)
  File "/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/acme/client.py", line 686, in post
    return self._post_once(*args, **kwargs)
  File "/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/acme/client.py", line 699, in _post_once
    return self._check_response(response, content_type=content_type)
  File "/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/acme/client.py", line 586, in _check_response
    raise messages.Error.from_json(jobj)
Error: urn:acme:error:malformed :: The request message was malformed :: DNS name does not have enough labels

after running this command:

./certbot-auto certonly -vvvv --standalone --dry-run --renew-with-new-domains -d www.my-domain.com -d my-domain.com -d localhost

Now I do not have any further idea. Is my bitnami.conf correct (see above)?

Please help.

silvio 2017-03-13 16:00:52 UTC #12

Hi,

Here you can find our updated documentation on how to create a certificate using let's encrypt.

And, answering your question, let's encrypt doesn't allow you to create certificates either for ip addresses or localhost.

Best regards,
Silvio Fernández

SvenS 2017-06-26 11:47:03 UTC #13

Many thanks for your reply and the new documentation.

I'm now back to this topic and still have the same problem: How can I access my PHPMyAdmin
https://127.0.0.1:8888/phpmyadmin/

If I try to use Firefox with this URL it returns:

Not Found
The requested URL ... was not found on this server.

Any advice?

jota 2017-06-27 11:09:51 UTC #14

In case you want to access your site using your domain and redirect all the request to that domain in case the user is not using it, you can follow this section in our documentation to achieve it

https://docs.bitnami.com/google/components/apache/#how-to-access-my-application-from-only-one-domain

It redirects all the request to your server but the ones to localhost or 127.0.0.1 to your domain. Please note that you'd need to remove the following lines from the .conf file and add the ones of the documentation

  ServerName 11.22.333.444
  ServerAlias www.my-domain.com my-domain.com
  Redirect "/" "https://my-domain.com/"

I hope it helps.
Jota

SvenS 2017-06-27 14:08:41 UTC #15

Hi Jota,

Many thanks for the information and reply. I have finally managed to access PHPmyadmin with some changes in the bitnami.conf file.
Now the only issue that remains, is that my browser wants to have an exception for bad server certificates. I guess this is due to the reason that the letsencrypt certificate only applies to the folder and URI of the WordPress installation.

/opt/bitnami/apps/wordpress/htdocs/ --> https://www.my-domain.com

But not to the folder of PHPmyadmin:

/opt/bitnami/apps/phpmyadmin/htdocs/ --> https://localhost:1234/phpmyadmin/

Is there any tutorial I can follow to manage that I will have a valid certificate for the folder of PHPmyadmin that is only accessable from a https://localhost:1234/phpmyadmin/ URI? In order to get rid of this bad server certificate issue.
Or is there any way to include the phpmyadmin into the letsencrypt certificate? So to say to get it under the umbrella of the existing certificate by somehow including it through configuration files settings or something?

Many thanks for your help.

jota 2017-06-28 10:26:27 UTC #16

As you are using a SSH tunnel to access phpMyAdmin in your instance, that connection is already secure so you don't need to use "https" when accessing phpMyAdmin. You can use "http://localhost:1234/phpmyadmin/"

In case you have a redirect rule to redirect everything from http to https, you can skip the localhost redirection by using this condition in the configuration files

RewriteCond %{HTTP_HOST} !^(localhost|127.0.0.1)

Best regards,
Jota

Was my answer helpful? Click on

SvenS 2017-06-28 12:11:56 UTC #17

Hi Jota,

Many thanks for your answer. It's good to know that things are secure anyhow.
Other than expected I still have this rule in my configuration file:
Redirect "/" "https://my-domain.com/"
I will leave it as is for now. I know it's working and I have to use http**s** & add an exception roule to Firefox and then everything is fine for me.

Now that everything is working, why would I need these lines in the configuration file anymore?

ServerName 11.22.333.444
ServerAlias www.my-domain.com my-domain.com

What do they do? What are they good for? Would they help or harm if I put them back in again?

But it still looks awful if third party developers have to work with it, I think.

Best,
Sven

jota 2017-06-29 09:57:47 UTC #18

I'm glad to hear that my information was useful for you. Regarding the ServerName and ServerAlias setting, you don't need to set them anymore. Please note that you set them in the main virtual host of Apache and that is the one that is run by Apache by default. In case you create a new VirtualHost, you can set them in order to tell Apache when to use that one instead of the default one.

https://httpd.apache.org/docs/2.4/mod/core.html#servername
https://httpd.apache.org/docs/2.4/mod/core.html#serveralias

Regards,
Jota

Powered by Discourse, best viewed with JavaScript enabled

Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now!

SugarCRM

Drupal

WordPress

Joomla!

Redmine