Navigation
- FAQ Home
- All categories
- About Webyog support and about this FAQ
- About the SQLyog program

- Connection issues
- Using the GUI
- Managing your MySQL Database Systems

- Database Schema Synchronization
- MySQL DATA synchronization
- SQL Scheduler and Reporting Tool
- Importing external data
- Backup/Restore
- SQLyog Job Agent (SJA)

- Working with Views, Stored Procedures and Triggers
- Character Set and Localization Issues
- MySQL bugs that affect SQLyog
- Questions on Open Source and Compiling
- Sitemap
Most popular FAQs 
- I get error 1130 "Host is not allowed to ... (169314 views)
- Error no. 2003: Can't connect... (86273 views)
- SQLyog Version History (63952 views)
- Error no. 1045: "Connection denied..." (61348 views)
- Error no. 1251: "Client does not support authentication..." (58317 views)
- Error No. 2005: Unknown MySQL server host... (50193 views)
- What is HTTP-tunneling? (42282 views)
- What Is SSH and SSH-tunneling? (38073 views)
- Can I use SQLyog with the WINE Windows emulator ... (34946 views)
- Why are Stored Procedures not created when I import ... (34267 views)
Latest FAQs 
- SQLyog Version History (2012-01-26 08:20)
- SQLyog is a client for the MySQL server - ... (2011-11-04 04:48)
- I get error 1130 "Host is not allowed to ... (2011-11-01 05:21)
- Problems on Ubuntu 11.x (2011-10-29 13:02)
- Problems creating a functional DSN on 64 bit Windows. ... (2011-09-15 14:34)
Sticky FAQs
Connection issues » HTTP(s)-tunneling
What should permissions be for the SQLyog tunneller file?
We recommend the permission setting for the SQLyog tunneller file to be (in octal notation) 644. That means read permission for both 'owner', 'group' and 'all' and write permission for 'owner' (only).
Actually no write permission is required at all, but public read permission most often is, if the webserver shall be able to use the file (unless the user/group structure is much different from the standard setups of most OS's). So also 444 works, but if you use this then you will need to change back in advance should you want to delete or replace it.
However we also have a few reports that settings higher than 644 like 664 (that additionally gives write access to 'group') in rare situations will raise an internal webserver error (reported as HTTP error 500 in a browser). Currently we are not sure about why it happens sometimes. It may be
* An issue with a specific OS
* Some special server directive in action
* Some special way the webserver is installed/configured in the OS
Any additional insight into this will be much appreciated!
br>Tags: -
Related entries:
- Do I need PHP to use SQLyog with MySQL?
- SQLyog gives you the most options for connecting to MySQL
- Welcome to the SQLyog FAQ
- Installation and upgrading
- Buying and Licensing SQLyog
Last update: 2008-09-09 07:09
Author: Peter Laursen
Revision: 1.0
You can comment this FAQ
Comment of Paul Kuczora:
Some hosting services (such as Hostgator) use this approach to enforce the use of "secure" file permissions on shared servers - e.g. to prevent someone over-writing your html files and possibly hijacking your site.
Found out the hard way installing ClickCartPro!
Permissions of 755 on html files would throw a 500 internal server error. On checking the server error log I found that the reason for the 500 error was the permissions on some files. Changing to 644 fixed the problem.
Added at: 2008-09-13 18:29