507 Insufficient Storage

Oblivion Knight

Oblivion Knight

Well-known member
I am just about ready to (re-)launch my website, but I am intermittently getting the standard error:
Oops! We ran into some problems.
Oops! We ran into some problems. Please try again later. More error details may be in the browser console.
Click to expand...


Looking at the browser console, the following is reported:
Code: 
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>507 Insufficient Storage</title> </head><body> <h1>Insufficient Storage</h1> <p>The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.  There is insufficient free space left in your storage allocation.</p> <p>Additionally, a 507 Insufficient Storage error was encountered while trying to use an ErrorDocument to handle the request.</p> </body></html> core-compiled.js:43:70
    defaultAjaxError https://nerdface.co.uk/js/xf/core-compiled.js:43:70    u https://nerdface.co.uk/js/xf/core-compiled.js:40:111    i https://nerdface.co.uk/js/vendor/jquery/jquery-3.2.1.min.js:2:28012    fireWith https://nerdface.co.uk/js/vendor/jquery/jquery-3.2.1.min.js:2:28783    A https://nerdface.co.uk/js/vendor/jquery/jquery-3.2.1.min.js:4:14058    c/< https://nerdface.co.uk/js/vendor/jquery/jquery-3.2.1.min.js:4:16323


Just wondered if anyone had any thoughts? Most recent changes are a change of PHP version to 7.2, and the installation of [TH] Spotify.
 
ThemeHouse indicate that it's likely to be the server I'm on that has ran out of disk space, despite my site taking a mere 192MB.

Seems like my shared hosting plan is over shared.. :notworthy:
 
Nerdface said:
I figured it would suffice while the site isn't even open, until it grows a bit..

Apparently not.
Click to expand...

It's not your site...it's them. First of all, unlimited doesn't exist. There is no such thing. Second of all, as I mentioned, your host is running their UK business off a Digital Ocean VPS.

It's just a matter of them upgrading their VPS to a higher plan, but until then you're stuck. Looks like the node has run out of disk space.
 
We have reviewed the provided information and we can confirm that currently there are no issues with your website and we are unable to recreate the reported issue, as it may have appeared only temporarily. In case you face similar issues again, please, contact us at the time it happens, by updating us on the exact error message received.
Click to expand...
😑 I don't think I'll be renewing in January..
 
Hello,

Thank you for your update.

We have reviewed your case and we found that your website has reached the following limits:

- Input/Output usage resources.

This value represents the amount of data that is read and/or written on the server's Hard Disk Drive. This value is usually increased when you make changes to your website, upload media, create new content or have an increased number of visitors.

We tested your side and currently, there seem to be no issues occurring.

In order to reduce the resource consumption we recommend the following actions:

  • Only use plugins you absolutely need for your website to function.
  • Check your plugins and find the ones which are using the most resources. There are several articles which could assist you further with this task.
  • Compress the images which your application has.
  • We can install Memcached for your site as it will help improve your site's speed and performance.
  • You can consider creating a Cloudflare account at the following link:

http://cloudflare.net

Considering the above, we would suggest contacting an experienced developer who would be able to review your website and optimize it for a Shared Hosting Environment.

Alternatively, you could consider upgrading your Hosting Package to a Cloud Hosting Package as it allows higher resources available:

Please do not hesitate to contact us again, if we can be of any further assistance. Our team is 24/7 at your immediate disposal!
Click to expand...
 
Switch hosts.

XF works fine on many shared server services, especially for a forum with such very low content/traffic such as yours.
 
Nerdface said:
On it.. Already signed up with none other than @WSWD
Click to expand...

Appreciate the sign-up! Was not expecting that. I'll get your discount taken care of as well. :)

There is no possible way your site is having any sort of real I/O issues. Either they don't know what they're doing, or their limits are set ridiculously low. Ugh! Hosts like this absolutely annoy me to no end.
 
It sounds like they’re not liking the number of reads being done with the Spotify addon, it’ll make an Ajax request every second (only for users that have associated their Spotify account) to update the current song details. This - especially only for a single user on a site that hasn’t launched yet - shouldn’t exceed any limits, but if you do encounter other issues you can try increasing the polling time in the options for the Spotify addon.
 
Last edited:
Jake B. said:
but if you do encounter other issues you can try increasing the polling time in the options for the Spotify addon.
Click to expand...
I was getting an intermittent "Not a JSON request" error - I can't remember the exact wording.

I've now tried changing the polling time to 2.5 seconds, see how we go..
 
Nerdface said:
I was getting an intermittent "Not a JSON request" error - I can't remember the exact wording.

I've now tried changing the polling time to 2.5 seconds, see how we go..
Click to expand...

If you have the exact error, I can look into it. Your site isn't having any resource issues or anything.
 
Jake B. said:
Anything in your Xf error log?
Click to expand...
Only one..


Stack:
Code: 
#0 src/vendor/guzzlehttp/guzzle/src/RequestFsm.php(103): GuzzleHttp\Exception\RequestException::wrapException(Object(GuzzleHttp\Message\Request), Object(GuzzleHttp\Ring\Exception\ConnectException))
#1 src/vendor/guzzlehttp/guzzle/src/RequestFsm.php(132): GuzzleHttp\RequestFsm->__invoke(Object(GuzzleHttp\Transaction))
#2 src/vendor/react/promise/src/FulfilledPromise.php(25): GuzzleHttp\RequestFsm->GuzzleHttp\{closure}(Array)
#3 src/vendor/guzzlehttp/ringphp/src/Future/CompletedFutureValue.php(55): React\Promise\FulfilledPromise->then(Object(Closure), NULL, NULL)
#4 src/vendor/guzzlehttp/guzzle/src/Message/FutureResponse.php(43): GuzzleHttp\Ring\Future\CompletedFutureValue->then(Object(Closure), NULL, NULL)
#5 src/vendor/guzzlehttp/guzzle/src/RequestFsm.php(134): GuzzleHttp\Message\FutureResponse::proxy(Object(GuzzleHttp\Ring\Future\CompletedFutureArray), Object(Closure))
#6 src/vendor/guzzlehttp/guzzle/src/Client.php(165): GuzzleHttp\RequestFsm->__invoke(Object(GuzzleHttp\Transaction))
#7 src/addons/ThemeHouse/Spotify/Util/Spotify/AbstractSpotify.php(120): GuzzleHttp\Client->send(Object(GuzzleHttp\Message\Request))
#8 src/addons/ThemeHouse/Spotify/Util/Spotify/Player.php(9): ThemeHouse\Spotify\Util\Spotify\AbstractSpotify->request('me/player')
#9 src/addons/ThemeHouse/Spotify/Service/Player/UpdatePlayback.php(36): ThemeHouse\Spotify\Util\Spotify\Player->getCurrentPlayback()
#10 src/addons/ThemeHouse/Spotify/Pub/Controller/Spotify.php(41): ThemeHouse\Spotify\Service\Player\UpdatePlayback->updateCurrentPlayback()
#11 src/XF/Mvc/Dispatcher.php(249): ThemeHouse\Spotify\Pub\Controller\Spotify->actionUpdateCurrentPlayback(Object(XF\Mvc\ParameterBag))
#12 src/XF/Mvc/Dispatcher.php(88): XF\Mvc\Dispatcher->dispatchClass('ThemeHouse\\Spot...', 'UpdateCurrentPl...', 'json', Object(XF\Mvc\ParameterBag), '', Object(ThemeHouse\Spotify\Pub\Controller\Spotify), NULL)
#13 src/XF/Mvc/Dispatcher.php(41): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#14 src/XF/App.php(1931): XF\Mvc\Dispatcher->run()
#15 src/XF.php(329): XF\App->run()
#16 index.php(13): XF::runApp('XF\\Pub\\App')
#17 {main}

-------------

Previous GuzzleHttp\Ring\Exception\ConnectException: cURL error 7: Failed to connect to api.spotify.com port 443: Connection timed out - src/vendor/guzzlehttp/ringphp/src/Client/CurlFactory.php:126
#0 src/vendor/guzzlehttp/ringphp/src/Client/CurlFactory.php(91): GuzzleHttp\Ring\Client\CurlFactory::createErrorResponse(Array, Array, Array)
#1 src/vendor/guzzlehttp/ringphp/src/Client/CurlHandler.php(96): GuzzleHttp\Ring\Client\CurlFactory::createResponse(Array, Array, Array, Array, Resource id #128)
#2 src/vendor/guzzlehttp/ringphp/src/Client/CurlHandler.php(68): GuzzleHttp\Ring\Client\CurlHandler->_invokeAsArray(Array)
#3 src/vendor/guzzlehttp/ringphp/src/Client/Middleware.php(54): GuzzleHttp\Ring\Client\CurlHandler->__invoke(Array)
#4 src/vendor/guzzlehttp/ringphp/src/Client/Middleware.php(30): GuzzleHttp\Ring\Client\Middleware::GuzzleHttp\Ring\Client\{closure}(Array)
#5 src/vendor/guzzlehttp/guzzle/src/RequestFsm.php(129): GuzzleHttp\Ring\Client\Middleware::GuzzleHttp\Ring\Client\{closure}(Array)
#6 src/vendor/guzzlehttp/guzzle/src/Client.php(165): GuzzleHttp\RequestFsm->__invoke(Object(GuzzleHttp\Transaction))
#7 src/addons/ThemeHouse/Spotify/Util/Spotify/AbstractSpotify.php(120): GuzzleHttp\Client->send(Object(GuzzleHttp\Message\Request))
#8 src/addons/ThemeHouse/Spotify/Util/Spotify/Player.php(9): ThemeHouse\Spotify\Util\Spotify\AbstractSpotify->request('me/player')
#9 src/addons/ThemeHouse/Spotify/Service/Player/UpdatePlayback.php(36): ThemeHouse\Spotify\Util\Spotify\Player->getCurrentPlayback()
#10 src/addons/ThemeHouse/Spotify/Pub/Controller/Spotify.php(41): ThemeHouse\Spotify\Service\Player\UpdatePlayback->updateCurrentPlayback()
#11 src/XF/Mvc/Dispatcher.php(249): ThemeHouse\Spotify\Pub\Controller\Spotify->actionUpdateCurrentPlayback(Object(XF\Mvc\ParameterBag))
#12 src/XF/Mvc/Dispatcher.php(88): XF\Mvc\Dispatcher->dispatchClass('ThemeHouse\\Spot...', 'UpdateCurrentPl...', 'json', Object(XF\Mvc\ParameterBag), '', Object(ThemeHouse\Spotify\Pub\Controller\Spotify), NULL)
#13 src/XF/Mvc/Dispatcher.php(41): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#14 src/XF/App.php(1931): XF\Mvc\Dispatcher->run()
#15 src/XF.php(329): XF\App->run()
#16 index.php(13): XF::runApp('XF\\Pub\\App')
#17 {main}


Request:
Code: 
array(4) {
  ["url"] => string(197) "/index.php?spotify/update-current-playback&_xfRequestUri=%2Fadmin.php%3Ftemplate-modifications%2F260%2Fedit&_xfWithData=1&_xfToken=1544134790%2C2253f1792ff02a306731d9b27a8cdb41&_xfResponseType=json"
  ["referrer"] => string(64) "https://nerdface.co.uk/admin.php?template-modifications/260/edit"
  ["_GET"] => array(5) {
    ["spotify/update-current-playback"] => string(0) ""
    ["_xfRequestUri"] => string(42) "/admin.php?template-modifications/260/edit"
    ["_xfWithData"] => string(1) "1"
    ["_xfToken"] => string(43) "1544134790,2253f1792ff02a306731d9b27a8cdb41"
    ["_xfResponseType"] => string(4) "json"
  }
  ["_POST"] => array(0) {
  }
}
 
You must log in or register to reply here.

Similar threads

werty
  • Locked
Not a bug Error changing the nodes permisson for a users gropu
Replies
1
Views
612
Paul B
Paul B
Brian Jones
Not a bug Having problem setting permissions.
Replies
1
Views
286
Brian Jones
Brian Jones
EIRE
  • Question Question
XF 2.2 Moved XF from subdomain to root
Replies
0
Views
480
EIRE
EIRE
Abraham54
  • Question Question
The main thread was blocked for 324 ms
Replies
6
Views
1K
Abraham54
Abraham54
Frode789
  • Suggestion Suggestion
Speed optimization/improvements in core XF
Replies
1
Views
1K
nodle
nodle
Top Bottom