Virtualmin>edit databases>manage tables> "404 file not found error" after upgrade from GPL to PRO

7 posts / 0 new
Last post
#1 Sun, 06/30/2019 - 05:47

Virtualmin>edit databases>manage tables> "404 file not found error" after upgrade from GPL to PRO

Hi guys,

  • Debian 9 VPS
  • 2CPU
  • 4GB Memory
  • Upgraded from GPL to Virtualmin pro (latest)

Virtualmin>Edit Databases> Manage Database> Edit Table

returns 404 "File not Found" error (displayed in virtualmin dashboard)


Webmin>Servers>MySQL Database Server>manage database>Edit Table

works no problems!

This server has just been upgrade from Virtualmin GPL to Virtualmin Pro (and this was working prior to the upgrade)

I also have modsecurity installed on this server.

Is it modsecurity that is likely causing this? (there is nothing in webmin apache error logs)

I have also checked other databases in Virtualmin...I am experiencing this 404 error with all of them when trying to access any tables...however they are all accessible from Webmin.

EDIT...if i create a new database in Virtualmin, i seem to be able to edit a new blank database from the Virtualmin tab. I can also update any of the existing wordpress websites that are using these databases, just not the existing databases from Virtualmin.

Mon, 07/01/2019 - 00:07


I unfortunately don't seem to be able to reproduce an issue like that.

If you restart Webmin, and/or shift-reload the site to refresh the cache, do you continue to see that issue?


Mon, 07/01/2019 - 18:47

This is in Virtualmin not Webmin. Webmin>Servers>MySQL Database Server ... is able to edit the databases no problems.

Take a look at the image links (1 & 2 are Virtualmin with the 404 error, 3 & 4 are Webmin without error)





I have run /etc/init.d/webmin stop /etc/init.d/webmin start

still returns a "404 file not found error" in virtualmin

would you like me to submit a support request through webmin>virtualmin technical support interface?

AJECreative is the home of $5 webhosting, $15/month VPS servers (1cpu,1gb RAM, 25GB storage)
Centos7, Debian9, or Ubuntu18LTS
Available Control Panels = Centos-Webpanel, Cyberpanel, or Virtualmin

Mon, 07/01/2019 - 18:56


Yup, I understand.

Note that Virtualmin is just a Webmin module.

Webmin didn't change when you upgraded though, only Virtualmin changed.

My goal is to ensure it's not just a temporary theme or cache issue that you're seeing, which could have occurred during the upgrade process.

By restarting the Webmin process, you are also restarting Virtualmin.

I'm hoping that you can try the troubleshooting steps mentioned in Comment #2 above, and let us know if those help.


Tue, 07/02/2019 - 02:04

Hi Eric, thanks for that information. Unfortunately, shift reload makes no difference. To double check, i jumped onto my wife's Imac (which has not been used for managing this server before)...i get the 404 file not found error on her Imac as well.

As a tripple check, i logged into the server using my Samsung Galaxy Note 10 mobile phone (with only its mobile sim internet connection...wifii disabled to ensure it wasnt using our office network connection)...virtualmin>Edit Databases>... Edit table produced "404 file not found error"

If you have any other thoughts I would appreciate if you could provide some pointers please.

I really wonder if the problem is me that seems like the most logical cause. Unfortunately, I am not sure how problem solve modsecurity issues when as far as i can tell, nothing is coming up in the apache error logs about this.

To explain the lack of entries in the virtualmin>Logs>Apache error logs point a little further...It is now 4.58pm here. I have in the last 15 minutes tried to open a database table using virtualmin on 3 different devices...all of which threw 404 error in Virtualmin dashboard interface.

The error logs for this virtualmin>virtual server show absolutely zip since 2.49:53s (2 hours ago)

I am confused as to how an error "inside Virtualmin itself" is not being logged?

I checked webmin mini serv logs...the last 20 lines are below...i dont see any relevance in any of these entries...

Subroutine parse_config_file redefined at /usr/share/webmin/fail2ban/ line 155.
Subroutine split_directive_values redefined at /usr/share/webmin/fail2ban/ line 205.
Subroutine create_section redefined at /usr/share/webmin/fail2ban/ line 226.
Subroutine modify_section redefined at /usr/share/webmin/fail2ban/ line 239.
Subroutine delete_section redefined at /usr/share/webmin/fail2ban/ line 250.
Subroutine section_lines redefined at /usr/share/webmin/fail2ban/ line 274.
Subroutine directive_lines redefined at /usr/share/webmin/fail2ban/ line 287.
Subroutine save_directive redefined at /usr/share/webmin/fail2ban/ line 300.
Subroutine find_value redefined at /usr/share/webmin/fail2ban/ line 403.
Subroutine find redefined at /usr/share/webmin/fail2ban/ line 410.
Subroutine filename_to_name redefined at /usr/share/webmin/fail2ban/ line 420.
Subroutine find_jail_by_filter redefined at /usr/share/webmin/fail2ban/ line 430.
Subroutine find_jail_by_action redefined at /usr/share/webmin/fail2ban/ line 446.
Subroutine start_fail2ban_server redefined at /usr/share/webmin/fail2ban/ line 465.
Subroutine stop_fail2ban_server redefined at /usr/share/webmin/fail2ban/ line 484.
Subroutine restart_fail2ban_server redefined at /usr/share/webmin/fail2ban/ line 502.
Subroutine list_all_config_files redefined at /usr/share/webmin/fail2ban/ line 510.
Subroutine lock_all_config_files redefined at /usr/share/webmin/fail2ban/ line 526.
Subroutine unlock_all_config_files redefined at /usr/share/webmin/fail2ban/ line 534.
Subroutine get_fail2ban_version redefined at /usr/share/webmin/fail2ban/ line 544.

AJECreative is the home of $5 webhosting, $15/month VPS servers (1cpu,1gb RAM, 25GB storage)
Centos7, Debian9, or Ubuntu18LTS
Available Control Panels = Centos-Webpanel, Cyberpanel, or Virtualmin

Tue, 07/02/2019 - 08:47


The issue you're seeing wouldn't be related to mod_security, as that works through Apache, and Webmin and Virtualmin don't use Apache... Webmin provides it's own web server, and Virtualmin makes use of that.

I unfortunately don't know what the issue there might be though, I haven't run into an issue like that in the past.

I think the best thing to do would be to file a bug report using the support tracker. That will allow us to get Jamie's input on that. Note that Jamie is currently traveling, but he'll respond as soon as he's available.


Tue, 07/02/2019 - 09:36

Someone else just reported a similar issue -- there's a bug report about that here now:

Topic locked