<p>One small detail that can cause the front-end and back-end of your site to result in a blank white page, is if you have a syntax error in your <code>general.php</code> file, such as a missing comma at the end of a line.  If you've just made a recent edit to your config files, take a closer look at them and make sure that you don't have any small errors.</p>

<p>For example, the following multi-environment config is missing a comma at the end of the <code>omitScriptNameInUrls</code> setting, and that minor detail would make both the front-end and back-end of a site result in a blank white page: </p>

<pre><code>return array(
    '*' =&gt; array(
        'omitScriptNameInUrls' =&gt; true
        'devMode' =&gt; false
    )
);
</code></pre>

CC BY-SA 3.0
2015-08-23T04:53:42.630Z
2015-08-23T04:53:42.630Z
Ben Parizek
<p>I have been unable to access my website or log into my CMS. I have checked with the server and everything is OK there but all I am getting is a blank page.</p>

<p>I updated craft manually following the instructions given.</p>

<p>I also have a staging site which I use for sharing with my client and this all works fine.</p>

<p>Is there anything I need to be checking? What will have stopped the website from working? I would really appreciate any help you can give with this.</p>

<p>Thanks in advance.</p>

CC BY-SA 3.0
2014-09-01T12:11:01.473Z
From your question I'm assuming that the site worked before an update, then it stopped working after the update. I'd either download the update manually, replace the app folder and set permissions, or submit a ticket to P&T including error logs.
darylknight
CC BY-SA 3.0
2014-09-01T14:56:22.207Z
Can you check your `craft/storage/runtime/logs` files and search them for any [error] or [warning] log entries that might be related to failed login attempts?
Brad Bell
CC BY-SA 3.0
2014-09-01T20:14:23.257Z
As far as I know the site was working fine before the update @codeknight. I also updated craft manually. I will check with the logs as suggested Brad and see whats what. Cheers for your help.
Patrick Wilbourne
CC BY-SA 3.0
2014-10-13T01:56:28.090Z
Did you ever get this resolved, @PatrickWilbourne?
Brad Bell
CC BY-SA 3.0
2015-02-20T02:13:25.317Z
@PatrickWilbourne, are you still out there?
Matt Stein
<control-panel>
Unable to access login page or my website
# Unable to access login page or my website

(Asked by: username_0 on 2014-09-01)

I have been unable to access my website or log into my CMS. I have checked with the server and everything is OK there but all I am getting is a blank page.

I updated craft manually following the instructions given.

I also have a staging site which I use for sharing with my client and this all works fine.

Is there anything I need to be checking? What will have stopped the website from working? I would really appreciate any help you can give with this.

Thanks in advance.

**Tags:** control-panel

> **Comments:**
> **username_1**: From your question I'm assuming that the site worked before an update, then it stopped working after the update. I'd either download the update manually, replace the app folder and set permissions, or submit a ticket to P&T including error logs.  
> **username_2**: Can you check your `craft/storage/runtime/logs` files and search them for any [error] or [warning] log entries that might be related to failed login attempts?  
> **username_0**: As far as I know the site was working fine before the update @codeknight. I also updated craft manually. I will check with the logs as suggested Brad and see whats what. Cheers for your help.  
> **username_2**: Did you ever get this resolved, @PatrickWilbourne?  
> **username_3**: @PatrickWilbourne, are you still out there?  

---

## 1 answers

### Answer by username_4 on 2015-08-23. Score: 3

One small detail that can cause the front-end and back-end of your site to result in a blank white page, is if you have a syntax error in your general.php file, such as a missing comma at the end of a line.  If you've just made a recent edit to your config files, take a closer look at them and make sure that you don't have any small errors.
For example, the following multi-environment config is missing a comma at the end of the omitScriptNameInUrls setting, and that minor detail would make both the front-end and back-end of a site result in a blank white page: 
return array(
    '*' => array(
        'omitScriptNameInUrls' => true
        'devMode' => false
    )
);


---

