If you are using Thin Pro 6.x image then this is known issue and the solution is to use Thin Pro 5.x
↧
If you are using Thin Pro 6.x image then this is known issue and the solution is to use Thin Pro 5.x