Restricted access — Joomla 1.5: Общие вопросы
Данная версия знаменует собой важную веху в разработке продукта. Из нововведений: множество улучшений, обеспечение повышенной производительности и расширенные функциональные возможности.
WT Revars insert
Плагин кнопки редактора для вставки шорт-кодов, созданных с помощью плагина Revars.
Статья «Как создать плагин для Joomla 4 для авторизации пользователя по email» (How to Create a.
Статья «Как создать плагин для Joomla 4 для авторизации пользователя по email» (How to Create a Joomla 4 Plugin to Allow User Login with Email)
The Joomla! Forum™
flynner Joomla! Apprentice
Posts: 10 Joined: Tue Apr 10, 2007 12:02 pm
Install error — Restricted access
Post by flynner » Tue Apr 10, 2007 12:20 pm
I’m very new to this CMS stuff so forgive my ignorance.
Here’s my problem, when I tried to install joomla to my server I followed all the steps and it appeared to work, I deleted the installation folder, then I tried viewing the site at http://76.162.9.143/index.php but I get this error
«Restricted accessRestricted accessRestricted accessRestricted accessRestricted access
Fatal error: Cannot instantiate non-existent class: database in /hsphere/local/home/stephenf/aquariussound.ie/includes/joomla.php on line 79″
I had the unwritable configuration.php issue but just copied it up manually. Also ixhosting is my host if that makes any difference.
pe7er Joomla! Master
Posts: 24169 Joined: Thu Aug 18, 2005 8:55 pm Location: Nijmegen, Netherlands Contact:
Re: Install error — Restricted access
Post by pe7er » Tue Apr 10, 2007 1:33 pm
barastanda Joomla! Fledgling
Posts: 1 Joined: Tue Apr 10, 2007 4:51 pm Contact:
Re: Install error — Restricted access
Post by barastanda » Tue Apr 10, 2007 4:56 pm
flynner Joomla! Apprentice
Posts: 10 Joined: Tue Apr 10, 2007 12:02 pm
Re: Install error — Restricted access
Post by flynner » Tue Apr 10, 2007 11:23 pm
Can I do that myself or do I need to ask my hosting company to do it?
pe7er Joomla! Master
Posts: 24169 Joined: Thu Aug 18, 2005 8:55 pm Location: Nijmegen, Netherlands Contact:
Re: Install error — Restricted access
Post by pe7er » Wed Apr 11, 2007 10:54 am
You can do that in FTP software (e.g. FileZilla).
Or ask your host.
Another thing you could check: Could you check if all necessary Joomla files are on the server?
Joomla Diagnostics is a helpful tool to check if all Joomla files have been uploaded correctly
http://extensions.joomla.org/component/ . Itemid,35/
flynner Joomla! Apprentice
Posts: 10 Joined: Tue Apr 10, 2007 12:02 pm
Re: Install error — Restricted access
Post by flynner » Wed Apr 11, 2007 11:07 am
Thanks for your help Peter,
It’s working now. I deleted the installation and started from scratch. This time I got my hosting company to fix all the permission before I went through the install steps.
pe7er Joomla! Master
Posts: 24169 Joined: Thu Aug 18, 2005 8:55 pm Location: Nijmegen, Netherlands Contact:
Re: Install error — Restricted access
Post by pe7er » Wed Apr 11, 2007 11:56 am
PS: Could you please mark your first message in this thread as «solved» ?
(Modify the first message and choose the Message Icon [solved] ).
This way the list of messages shows that the question has been solved, and other users can benefit from it.
thanjeys Joomla! Apprentice
Posts: 9 Joined: Wed Jul 16, 2008 7:15 am
Re: Install error — Restricted access
Post by thanjeys » Wed Jul 16, 2008 7:26 am
I am new bie to Joomla . I just transferred joomla1.0 in my own server!! I got error message..
— Restricted accessRestricted accessRestricted accessRestricted accessRestricted access
can u explain!! what r the file shud i change permission !!
But now changed permission in some folder
administrator/
cache/
images/
includes/
media/
templates/
mambots/
language/
modules/
even i got same error messgae .
eratl Joomla! Apprentice
Posts: 21 Joined: Fri Apr 06, 2007 2:40 pm
Re: Install error — Restricted access-
Post by eratl » Thu Jul 24, 2008 6:47 pm
I was following some instructions to diagnose problems accessing some areas of my site using the diagnotics tool. Here’s the information I tried to follow:
REGISTER GLOBALS EMULATION
By default, Joomla will emulate register_globals = on, to not brake backwards compatibility with older components, modules or plugins. This will cause the same security issues as using normal register_globals on. You can turn this off however.
Open globals.php located in the root of your joomla installation. Search for:
define( ‘RG_EMULATION’, 1 );
and change it to:
define( ‘RG_EMULATION’, 0 );
That should keep you a bit safer against attacks.
The problem: After changing the global.php from ( ‘RG_EMULATION’, 1 ); to ( ‘RG_EMULATION’, 0 );, I now get this error when trying to access my login:
I changed it back to ( ‘RG_EMULATION’, 1 ); but still cannot get into my control panel. When I go to mysite/administrator/index2.php, I get the login page and can imput my login and password. That’s when I get the Restricted Access message. To my knowledge, the globals.php file is the only one I changed. I’ve even copied what I believe was the original globals.php file back to the root directory but continue to get the Restricted Access. Any Idea what I could have done wrong?
Here’s my actual gobals.php file content that’s on the server:
<?php
/**
* @version $Id: globals.php 4675 2006-08-23 16:55:24Z stingrey $
* @package Joomla
* @copyright Copyright (C) 2005 Open Source Matters. All rights reserved.
* @license http://www.gnu.org/copyleft/gpl.html GNU/GPL, see LICENSE.php
* Joomla! is free software and parts of it may contain or be derived from the
* GNU General Public License or other free or open source software licenses.
* See COPYRIGHT.php for copyright notices and details.
*/
// no direct access
defined( ‘_VALID_MOS’ ) or die( ‘Restricted access’ );
/**
* Use 1 to emulate register_globals = on
* WARNING: SETTING TO 1 MAY BE REQUIRED FOR BACKWARD COMPATIBILITY
* OF SOME THIRD-PARTY COMPONENTS BUT IS NOT RECOMMENDED
*
* Use 0 to emulate regsiter_globals = off
* NOTE: THIS IS THE RECOMMENDED SETTING FOR YOUR SITE BUT YOU MAY
* EXPERIENCE PROBLEMS WITH SOME THIRD-PARTY COMPONENTS
*/
define( ‘RG_EMULATION’, 0 );
/**
* Adds an array to the GLOBALS array and checks that the GLOBALS variable is
* not being attacked
* @param array
* @param boolean True if the array is to be added to the GLOBALS
*/
function checkInputArray( &$array, $globalise=false ) <
static $banned = array( ‘_files’, ‘_env’, ‘_get’, ‘_post’, ‘_cookie’, ‘_server’, ‘_session’, ‘globals’ );
foreach ($array as $key => $value) <
$intval = intval( $key );
// PHP GLOBALS injection bug
$failed = in_array( strtolower( $key ), $banned );
// PHP Zend_Hash_Del_Key_Or_Index bug
$failed |= is_numeric( $key );
if ($failed) <
die( ‘Illegal variable <b>’ . implode( ‘</b> or <b>’, $banned ) . ‘</b> passed to script.’ );
>
if ($globalise) <
$GLOBALS[$key] = $value;
>
>
>
/**
* Emulates register globals = off
*/
function unregisterGlobals () <
checkInputArray( $_FILES );
checkInputArray( $_ENV );
checkInputArray( $_GET );
checkInputArray( $_POST );
checkInputArray( $_COOKIE );
checkInputArray( $_SERVER );
if (isset( $_SESSION )) <
checkInputArray( $_SESSION );
>
$REQUEST = $_REQUEST;
$GET = $_GET;
$POST = $_POST;
$COOKIE = $_COOKIE;
if (isset ( $_SESSION )) <
$SESSION = $_SESSION;
>
$FILES = $_FILES;
$ENV = $_ENV;
$SERVER = $_SERVER;
foreach ($GLOBALS as $key => $value) <
if ( $key != ‘GLOBALS’ ) <
unset ( $GLOBALS [ $key ] );
>
>
$_REQUEST = $REQUEST;
$_GET = $GET;
$_POST = $POST;
$_COOKIE = $COOKIE;
if (isset ( $SESSION )) <
$_SESSION = $SESSION;
>
$_FILES = $FILES;
$_ENV = $ENV;
$_SERVER = $SERVER;
>
/**
* Emulates register globals = on
*/
function registerGlobals() <
checkInputArray( $_FILES, true );
checkInputArray( $_ENV, true );
checkInputArray( $_GET, true );
checkInputArray( $_POST, true );
checkInputArray( $_COOKIE, true );
checkInputArray( $_SERVER, true );
if (isset( $_SESSION )) <
checkInputArray( $_SESSION, true );
>
foreach ($_FILES as $key => $value) <
$GLOBALS[$key] = $_FILES[$key][‘tmp_name’];
foreach ($value as $ext => $value2) <
$key2 = $key . ‘_’ . $ext;
$GLOBALS[$key2] = $value2;
>
>
>
if (RG_EMULATION == 0) <
// force register_globals = off
unregisterGlobals();
> else if (ini_get(‘register_globals’) == 0) <
// php.ini has register_globals = off and emulate = on
registerGlobals();
> else <
// php.ini has register_globals = on and emulate = on
// just check for spoofing
checkInputArray( $_FILES );
checkInputArray( $_ENV );
checkInputArray( $_GET );
checkInputArray( $_POST );
checkInputArray( $_COOKIE );
checkInputArray( $_SERVER );
if (isset( $_SESSION )) <
checkInputArray( $_SESSION );
>
>
?>
Restricted access joomla как исправить
Чтобы возвратить доступ к Вашему бэкенду после активирования AdminExile, Вы должны переименовать файл модуля, используя SSH или (s) FTP. Перейдите в каталог plugins/system Вашей Joomla и найдите каталог adminexile. В том каталоге найдите файл «adminexile.php» и переименуйте его. Например, достаточно Добавить «x» к имени файла (adminexilex.php).
Когда имя файла изменено, плагин не может работать, и Вы возвратите доступ к своему сайту. В этом пункте Вы должны сбросить ключ доступа (access key) для adminexile, после чего и изменить имя файла назад на adminexile.php.
Если Вы хотите удалить adminexile, отключите плагин, используя опцию публикации во вставной конфигурации или кнопки во вставном списке. Перед удалением переименуйте adminexile.php файл назад к его настоящему имени, затем удалите плагин стандартным способом.
[Блокировка доступа в панель администратора]
Если сервер в ответ на попытку открыть ссылку, ведущую к backend Joomla (админка, система администрирования сайта) http://имя_домена/administrator/index.php мгновенно выдает сообщение «Forbidden You don’t have permission to access /administrator/index.php on this server.», то скорее всего в папке administrator присутствует файл .htaccess, в котором прописаны правила блокирования по IP. Например, содержание файла .htaccess может быть таким:
Если Ваш IP, с которого Вы пытаетесь открыть админку (т. е. файл, который находится в каталоге administrator, где лежит этот файл .htaccess), не соответствует этим правилам (IP не начинается на 78.46, или не равен 32.101.72.112), то Apache сразу заблокирует доступ с сообщением «Forbidden . «.
Restricted access joomla как исправить
joomla site showing restricted access
I am having one problem with this site http://onlinecasinosouthafrica.co.za/ in joomla. I just change the site global configuration from admin beside that working to submit a form to send mail. I don,t know the reason behind now my site is showing restricted access. May be due to change of global configuration as I have changed the Use Apache mod_rewrite option from no to yes, though after that I have worked and refresh the page it was showing clearly now it is showing restricted access only. unable to understand what is going on.Please help me in this.
thanks in advance.
1 Answer 1
At the top of every .php file in a Joomla site you will see something similar to this:
This is here to prevent anyone accessing the file directly via the browser. It basically says: If the _JEXEC constant is not defined, kill the process, _JEXEC is set when the application is run, it happens in the sites main index.php file near the top:
If this is removed, it will definetely cause those issues, but most likely the error is resulting from a component or plugin that is published in the CMS.
If you have installed a plugin that was meant for Joomla 1.0, you will see an error like this, this happens because rather that looking for _JEXEC being set, it looks for something like _VALID_MOS, in this case, try switching legacy mode plugin on.
If Legacy mode does not fix your issue, check the website template to ensure the defined(‘_JEXEC’) or die(‘Restricted Access’); line is not causing issues, comment it out with a # or // and test that.
You could try switching the Joomla debug on, but there is no guarantee that will help.
If you are really stuck, you can try one of the following:
1) Backup database, then disable all of the plugins one by one (I noticed you still have access to the administrator area), then either re-enable the plugins or restore the database.
2) I once had to do a find and replace of every plugin in a CMS, I replaced the string:
I done this using PHP and it allowed me to pinpoint exactly which file was throwing the error. I obviously backed up the site file structure first, so I simply unzipped the backup and deleted the modified files later.