Symfony 500 internal server error - Исправление ошибок и поиск оптимальных решений проблем

Edit this page

Troubleshooting

How to access the Application Logs?

Display the application log file via:

Any log messages generated by the application is sent to this app file. This includes language errors such as PHP Errors, Warnings, and Notices, as well as uncaught exceptions.

It also contains your application logs if you log on stderr.

Because Platform.sh manages this file for you (preventing disks to get filled and using very fast local drives instead of slower network disk), we recommend that applications always output their log to stderr. For Monolog, check config/packages/prod/monolog.yaml:

If you log deprecations, don’t forget to log them on stderr as well.

Oops! An Error Occurred

This error message comes from your application and is generated by the default Symfony’s error template.

The server returned a «500 Internal Server Error»

If your application works locally but you see this message on Platform.sh it usually means you have a configuration error or missing a dependency.

To fix this issue you have to inspect application logs, the cause of the error is usually specified in the error message:

If the error happens on a non production environment or on the main environment of a non production project you can also enable Symfony’s dev/debug mode to inspect the cause of the error:

The server returned a «404 Not Found»

New Symfony applications comes without controllers by default. This means there’s no page to show as a homepage. When running your project locally you should have been welcomed with this page:

But with this page when running on Platform.sh:

This is because Platform.sh runs in production mode and as such Symfony shown a generic 404 error. To fix this, you will have to create your first Symfony page.

If you already created a custom page, check that all your files are committed, that you ran symfony deploy and it succeeded.

Источник

Comments

Symfony version(s) affected: 4.4.*

Description
When you have the wrong configuration, instead of showing exceptions, an 500 page is displayed.
This problem does not depend on the environment.

How to reproduce
Just set malformed *.ymal file something like this :

# config/routes/annotations.yaml
;321-

What else would you expect? If the app is broken, a 500 is the correct display, isn’t it?
If you mean that you’d expect a nice customized error page, that’s not possible: because the config is broken, the nice error page cannot be configured…

In debug mode, it shows a LoaderLoadException, telling you which file contains malformed YAML.

ParseException > InvalidArgumentException > LoaderLoadException
HTTP 500 Internal Server Error 

The file "config/routes/annotations.yaml" does not contain valid YAML in config/routes/annotations.yaml (which is loaded in resource "config/routes/annotations.yaml").

You can’t compile the container, so you can’t register an ExceptionListener that would do anything else. I’m not sure how you could do anything else at the Symfony level. You could use your webserver (e.g. nginx or Apache) to intercept 500 errors and show something more end-user friendly, but I’d first try to change the workflow so I don’t need to handle broken YAML files in production.

!!! Sorry for may very bad english !!!

@nicolas-grekas I expect at least two things:

possability to see errors in debug mode.
possability to change error page.

This is a very annoying problem because not all errors are displayed.

@blowski It is on symfony level. error-hanlder composent overwrites all server and php configurations.

when you have error in routes/*.yaml if you have this page:

This page generated in SymfonyComponentErrorHandlerErrorRendererHtmlErrorRenderer and not correct pass $debug __construct parameter.

After small but very stupid fix something like this :

#vendor/symfony/error-handler/ErrorRenderer/HtmlErrorRenderer.php
...
 /**
     * @param bool|callable $debug        The debugging mode as a boolean or a callable that should return it
     * @param bool|callable $outputBuffer The output buffer as a string or a callable that should return it
     */
    public function __construct($debug = false, string $charset = null, $fileLinkFormat = null, string $projectDir = null, $outputBuffer = '', LoggerInterface $logger = null)
    {

        if (!is_bool($debug) && !is_callable($debug)) {
            throw new TypeError(sprintf('Argument 1 passed to "%s()" must be a boolean or a callable, "%s" given.', __METHOD__, is_object($debug) ? get_class($debug) : gettype($debug)));
        }

        if (!is_string($outputBuffer) && !is_callable($outputBuffer)) {
            throw new TypeError(sprintf('Argument 5 passed to "%s()" must be a string or a callable, "%s" given.', __METHOD__, is_object($outputBuffer) ? get_class($outputBuffer) : gettype($outputBuffer)));
        }
##< FORCE CHECK  DEBUG ENV
  if(getenv('APP_ENV') != 'prod' 
            OR getenv('APP_DEBUG') == 1
            OR (isset($_SERVER['APP_DEBUG']) AND $_SERVER['APP_DEBUG'] == 1) 
        ){
            $debug = true;
        }
##> FORCE CHECK  DEBUG ENV
        $this->debug = $debug;
        $this->charset = $charset ?: (ini_get('default_charset') ?: 'UTF-8');
        $this->fileLinkFormat = $fileLinkFormat ?: (ini_get('xdebug.file_link_format') ?: get_cfg_var('xdebug.file_link_format'));
        $this->projectDir = $projectDir;
        $this->outputBuffer = $outputBuffer;
        $this->logger = $logI can't overwrite  `error_handler.error_renderer.html` service. In my case i just replace SymfonyComponentErrorHandlerErrorRenderer namesapce in composer whit my own file. ger;
    }
...

i have this page :

I can’t overwrite error_handler.error_renderer.html service. In my case i just replace SymfonyComponentErrorHandlerErrorRenderer namesapce in composer whit my own stupid fix class.

Thanks for the update.

I just did the following:

clean install of Symfony 4.4
entered invalid Yaml in config/routes/annotations.yaml
load in the browser (Symfony webserver)

I get the «nice error page» you showed in your comment, which leads me to think you have a configuration problem. Can you use xdebug (or at least dd(debug_backtrace())) to figure out what’s being passed to HtmlErrorRenderer? It sounds like maybe you’ve got debug mode disabled in dev.

@blowski like this ?

  0 => array:7 [▼
    "file" => "/repos/Tutorials/ApiPlatform/PaerOne/lesson1/start/vendor/symfony/error-handler/ErrorHandler.php"
    "line" => 707
    "function" => "__construct"
    "class" => "SymfonyComponentErrorHandlerErrorRendererHtmlErrorRenderer"
    "object" => SymfonyComponentErrorHandlerErrorRendererHtmlErrorRenderer {#3637 ▼
      -debug: null
      -charset: null
      -fileLinkFormat: null
      -projectDir: null
      -outputBuffer: null
      -logger: null
    }
    "type" => "->"
    "args" => array:1 [▼
      0 => false
    ]
  ]

Yes, that’s really useful, thanks. Go back through the whole backtrace and figure out why debug is either null or false — it should be true in the dev environment.

Some pointers:

The .env file should have a line like APP_ENV: dev.
In public/index.php you should see something like if($_SERVER['APP_DEBUG']) { Debug::enable(); }.
$_SERVER['APP_DEBUG'] is set in config/bootstrap.php.

Yes, you should be able to see the detailed exception page if the debug mode is enabled only. Please, check the @blowski’s comment above.

@blowski Everything is standard. The problem is that SymfonyComponentErrorHandlerErrorRendererHtmlErrorRenderer does not pass parameters when there is a syntax error.

I think the problem is that error_handler.error_renderer.html expects a data request service as a $debug parameter when there is a syntax error.

    <services>
        <service id="error_handler.error_renderer.html" class="SymfonyComponentErrorHandlerErrorRendererHtmlErrorRenderer">
            <!-- < This is not possible to execute when we have sytax error  -->

            <argument type="service">
                <service>
                    <factory class="SymfonyComponentErrorHandlerErrorRendererHtmlErrorRenderer" method="isDebug" />
                    <argument type="service" id="request_stack" />
                    <argument>%kernel.debug%</argument>
                </service>
            </argument>
            <!-- This is not possible to execute when we have sytax error  >-->

            <argument>%kernel.charset%</argument>
            <argument type="service" id="debug.file_link_formatter" on-invalid="null" />
            <argument>%kernel.project_dir%</argument>
            <argument type="service">
                <service>
                    <factory class="SymfonyComponentErrorHandlerErrorRendererHtmlErrorRenderer" method="getAndCleanOutputBuffer" />
                    <argument type="service" id="request_stack" />
                </service>
            </argument>
            <argument type="service" id="logger" on-invalid="null" />
        </service>

        <service id="error_renderer.html" alias="error_handler.error_renderer.html" />
        <service id="error_renderer" alias="error_renderer.html" />
    </services>

I can’t reproduce your problem from this side, so I can’t really do much to help debug. For me, with a clean install running in dev, I get a full error message.

Are you getting full error message only for malformed YAML, or for all other errors as well?

The only next steps I can think of are to try doing a clean install on your environment to see if there’s something weird going on that’s producing an edge case.

@ikakarov the html error renderer won’t work as service because there is a config error, so the container compilation process is broken. However, there is a fallback mechanism to catch that errors: see ErrorHandler::renderException() -> new HtmlErrorRenderer($this->debug).

You should see the exception page if $this->debug is true, and that will happen only if debug mode (Debug::enable()) is called on your front.

@yceruto Thanks.

I don’t get why @ikakarov is not experiencing all sorts of weirdness if not in debug mode.

I am going to close here for now due to the lack of feedback. Please let us know when you have more information and we can consider to reopen.

I upgraded from symfony 3.4 to 4.4.10 and ever since, sometimes I get a nice error page showing the exception, and sometimes I just get the 500 error page. Luckily I have sentry to report me the errors, for instance now it shows error 500 without any additional info, and sentry reports:

Object of class DoctrineORMPersistentCollection could not be converted to string

Output of dd(debug_backtrace()) returns:

 [▼
    "file" => "/Users/home/project/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php"
    "line" => 80
    "function" => "handleRaw"
    "class" => "SymfonyComponentHttpKernelHttpKernel"
    "object" => SymfonyComponentHttpKernelHttpKernel {#607 ▼
      #dispatcher: SymfonyComponentHttpKernelDebugTraceableEventDispatcher {#602 …8}
      #resolver: SymfonyComponentHttpKernelControllerTraceableControllerResolver {#518 ▼
        -resolver: SymfonyBundleFrameworkBundleControllerControllerResolver {#517 ▼
          #parser: SymfonyBundleFrameworkBundleControllerControllerNameParser {#647 ▼
            #kernel: AppKernel {#17 ▼
              #bundles: array:35 [▶]
              #container: Container0EKP23gappAppKernelDevDebugContainer {#63 …20}
              #rootDir: "/Users/home/project/app"
              #environment: "dev"
              #debug: true
              #booted: true
              #name: "app"
              #startTime: 1597215689.1078
              -projectDir: null
              -warmupDir: null
              -requestStackSize: 1
              -resetServices: true
            }
          }
...
]

After reading above, I don’t have any .env file, I tried adding one with value of: APP_ENV=dev and no difference. I have Debug::enable() and new AppKernel('dev', true) in app_dev.php

How can I fix this, it’s really annoying issue for me.

After searching a bit in code, I found out that this line is maybe the reason it doesn’t catch exceptions. As of php 7, errors are not reported using traditional error mechanisms, but reported as exception of type Error.

To test this, I just changed Exception to Error, and the exception is displayed.

#36254 (comment) — This solution is tested and worked, i just changed this

} catch (Exception $e) {

to this

 } catch (Exception|Error $e) {

at line 85. But this solution is not optimal, and I’m not convinced it will work everywhere.

Still facing this annoying issue, should I open a new issue?

Still facing this annoying issue, should I open a new issue?

Same issue for me

I upgraded from symfony 3.4 to 4.4.10

Can you check which Debug::enable() call you have in your front controller ? Symfony 4.4 contains 2 such classes:

the old one SymfonyComponentDebugDebug
the new one SymfonyComponentErrorHandlerDebug

Maybe the issue happens only when using the old Debug class (i.e. when upgrading Symfony without updating the front controller) ?

Herz3h, msieracki00, vanssata, Nek-, MJBGO, sebwr, GSpecDrum, AngryUbuntuNerd, buffcode, GeoffreyBidi, and 5 more reacted with thumbs up emoji
lasarian27 reacted with hooray emoji
Herz3h, Nek-, MJBGO, CharlyPoppins, mokabyls, sebwr, theredled, MartinStrekelj, GeoffreyBidi, Lukeboy25, and lasarian27 reacted with heart emoji

Debug::enable

That was it, thank you very much!!

@nicolas-grekas looks like something is still wrong in the BC layer when using the old component. It might be good to fix it if possible.

This comment has been minimized.

I can confirm the problem coming from 4.0 to 4.4 The debug page is not shown when using

SymfonyComponentDebugDebug

instead of

SymfonyComponentErrorHandlerDebug

I am not able to reproduce the described issue. Can someone of you please create a small example application that allows to do so?

I am going to close here for now due to the lack of feedback. Please let us know when you have more information and we can consider to reopen.

Источник

Compile Error: SymfonyComponentDebugDebugClassLoader::loadClass(): Failed opening required ‘/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/composer/../../src/PrestaShopBundle/Controller/Admin/AttachementProductController.php’ (include_path=’/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/tools/htmlpurifier/standalone:/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/pear/pear_exception:/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/pear/console_getopt:/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/pear/pear-core-minimal/src:/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/pear/archive_tar:.:/usr/share/php:/usr/share/pear’)

500 Internal Server Error — FatalErrorException

Stack Trace

in vendor/symfony/symfony/src/Symfony/Component/Debug/DebugClassLoader.php at line 171
1. if ($this->isFinder && !isset($this->loaded[$class])) {
2. $this->loaded[$class] = true;
3. if ($file = $this->classLoader[0]->findFile($class)) {
4. require $file;
5. }
6. } else {
7. call_user_func($this->classLoader, $class);

INFO — The SensioBundleDistributionBundleControllerConfiguratorController class extends SymfonyComponentDependencyInjectionContainerAware that is deprecated since version 2.8, to be removed in 3.0. Use the ContainerAwareTrait instead.
CRITICAL — Uncaught PHP Exception SymfonyComponentDebugExceptionFatalErrorException: «Compile Error: SymfonyComponentDebugDebugClassLoader::loadClass(): Failed opening required ‘/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/composer/../../src/PrestaShopBundle/Controller/Admin/AttachementProductController.php’ (include_path=’/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/tools/htmlpurifier/standalone:/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/pear/pear_exception:/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/pear/console_getopt:/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/pear/pear-core-minimal/src:/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/pear/archive_tar:.:/usr/share/php:/usr/share/pear’)» at /var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/symfony/symfony/src/Symfony/Component/Debug/DebugClassLoader.php line 171
DEBUG — Notified event «kernel.request» to listener «SymfonyComponentHttpKernelEventListenerDebugHandlersListener::configure».
DEBUG — Notified event «kernel.request» to listener «SymfonyComponentHttpKernelEventListenerProfilerListener::onKernelRequest».
DEBUG — Notified event «kernel.request» to listener «SymfonyComponentHttpKernelEventListenerValidateRequestListener::onKernelRequest».
DEBUG — Notified event «kernel.request» to listener «SymfonyBundleFrameworkBundleEventListenerSessionListener::onKernelRequest».
DEBUG — Notified event «kernel.request» to listener «SymfonyComponentHttpKernelEventListenerFragmentListener::onKernelRequest».
DEBUG — Notified event «kernel.request» to listener «SymfonyComponentHttpKernelEventListenerRouterListener::onKernelRequest».
DEBUG — Notified event «kernel.request» to listener «SymfonyComponentHttpKernelEventListenerLocaleListener::onKernelRequest».
DEBUG — Notified event «kernel.request» to listener «PrestaShopBundleEventListenerUserLocaleListener::onKernelRequest».
DEBUG — Notified event «kernel.request» to listener «SymfonyComponentHttpKernelEventListenerTranslatorListener::onKernelRequest».
DEBUG — Notified event «kernel.request» to listener «SymfonyComponentSecurityHttpFirewall::onKernelRequest».
DEBUG — Notified event «kernel.request» to listener «PrestaShopPrestaShopAdapterSecurityAdmin::onKernelRequest».
DEBUG — Notified event «kernel.request» to listener «PrestaShopPrestaShopAdapterSecuritySslMiddleware::onKernelRequest».
DEBUG — Notified event «kernel.request» to listener «PrestaShopBundleEventListenerTokenizedUrlsListener::onKernelRequest».
WARNING — realpath(): open_basedir restriction in effect. File(/) is not within the allowed path(s): (/var/www/vhosts/hosting101292.af98b.netcup.net/:/tmp/)
DEBUG — Notified event «kernel.controller» to listener «SymfonyBundleFrameworkBundleDataCollectorRouterDataCollector::onKernelController».
DEBUG — Notified event «kernel.controller» to listener «SymfonyComponentHttpKernelDataCollectorRequestDataCollector::onKernelController».
DEBUG — Notified event «kernel.controller» to listener «SensioBundleFrameworkExtraBundleEventListenerControllerListener::onKernelController».
DEBUG — Notified event «kernel.controller» to listener «SensioBundleFrameworkExtraBundleEventListenerParamConverterListener::onKernelController».
DEBUG — Notified event «kernel.controller» to listener «SensioBundleFrameworkExtraBundleEventListenerHttpCacheListener::onKernelController».
DEBUG — Notified event «kernel.controller» to listener «SensioBundleFrameworkExtraBundleEventListenerSecurityListener::onKernelController».
DEBUG — Notified event «kernel.controller» to listener «SensioBundleFrameworkExtraBundleEventListenerTemplateListener::onKernelController».

Stack Trace (Plain Text)

[1] SymfonyComponentDebugExceptionFatalErrorException: Compile Error: SymfonyComponentDebugDebugClassLoader::loadClass(): Failed opening required '/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/composer/../../src/PrestaShopBundle/Controller/Admin/AttachementProductController.php' (include_path='/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/tools/htmlpurifier/standalone:/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/pear/pear_exception:/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/pear/console_getopt:/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/pear/pear-core-minimal/src:/var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/pear/archive_tar:.:/usr/share/php:/usr/share/pear')
    at n/a
        in /var/www/vhosts/hosting101292.af98b.netcup.net/httpdocs/tumatsch-leder/vendor/symfony/symfony/src/Symfony/Component/Debug/DebugClassLoader.php line 171

I’m really confused right now. I’m not a pro and my English is also not the best.
Can somebody explain me where is there problem and how I can fix it?

Thank you!

cheers.
-Alex

Share this post

Link to post

Share on other sites

wowsushi

Newbie

Share this post

Link to post

Share on other sites

Auto-Dress

Newbie

I fixed the problem.
I don’t know why, but the AttachementProductController.php was deleted.

Download Prestashop and look after AttachementProductController.php in src/PrestaShopBundle/Controller/Admin/AttachementProductController.php

paste the AttachementProductController.php in your folder on your host. (your shop/

src/PrestaShopBundle/Controller/Admin/

I hope I could help.

Share this post

Link to post

Share on other sites

wowsushi

Newbie

Couldn’t find any AttachementProductController.php I got there: AdminAttachmentsController.php

Thats it. Wich version u got?

Mine is 1.7.4.2

Share this post

Link to post

Share on other sites

Auto-Dress

Newbie

my version is 1.7.4.2 too

You can’t find it cause it was deleted I think.

here is my solution.

you can see on the pictures where you have to go.
On the last picture you see there have to be the AttachementProductController.php

If not, you have to insert the AttachementProductController.php in the attachment down below.

Hope it works.

AttachementProductController.php

Share this post

Link to post

Share on other sites

1 year later…

sergisala

Newbie

Hi, I have the same problem as you and I do have the AttachementProductController.php file. Is there any other solution?

Share this post

Link to post

Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Sign in

Already have an account? Sign in here.

Источник

Hi,

I’ve recently been trying to learn more about VM’s and vagrant, i’m also relatively new to Nginx as most development I have done in the passed has been on Apache.

Anyway, I’m trying to setup a new Symfony project on my local under a workspace directory, within this directory I have several other projects too.

I am able to run composer install and install the framework. I can go to the following endpoint: http://workspace.dev/symfony/web/app.php and see the «Welcome to symfony 3.2.2» page. However when I create a new route such as /test:

/**
 * @Route("/test", name="test")
 */
public function testAction(Request $request)
{
    die('Hello world, welcome to the test page!');
}

and then go to: http://workspace.dev/symfony/web/app.php/test I get a Nginx 500 error.

I’m not sure what I should do to resolve the issue or if I have missed something in the setup.

I don’t think this is a routing or .htaccess issue as it is is a blank install and i’m using: SensioBundleFrameworkExtraBundleConfigurationRoute

I though maybe I need to setup a new vhost for the project like: project.dev/test which points to > http://workspace.dev/symfony/web/app.php

but had no success.

Would be really grateful of any help

I’m using puphpet to generate my vagrant files etc. the config is like so:

vagrantfile:
    target: local
    vm:
        provider:
            local:
                box: puphpet/ubuntu1404-x64
                box_url: puphpet/ubuntu1404-x64
                box_version: '0'
                chosen_virtualizer: virtualbox
                virtualizers:
                    virtualbox:
                        modifyvm:
                            natdnshostresolver1: false
                        showgui: 0
                    vmware:
                        numvcpus: 1
                    parallels:
                        linked_clone: 0
                        check_guest_tools: 0
                        update_guest_tools: 0
                machines:
                    vflm_75yfxsvwnabf:
                        id: machine1
                        hostname: machine1.puphpet
                        network:
                            private_network: 192.168.56.101
                            forwarded_port:
                                vflmnfp_8bx6f11n3o9p:
                                    host: '7373'
                                    guest: '22'
                        memory: '512'
                        cpus: '1'
        provision:
            puppet:
                manifests_path: puphpet/puppet/manifests
                module_path:
                    - puphpet/puppet/modules
                    - puphpet/puppet/manifests
                options:
                    - '--verbose'
                    - '--hiera_config /vagrant/puphpet/puppet/hiera.yaml'
        synced_folder:
            vflsf_53kwyzt6imrw:
                source: ./
                target: /var/www
                sync_type: nfs
                smb:
                    smb_host: ''
                    smb_username: ''
                    smb_password: ''
                    mount_options:
                        dir_mode: '0775'
                        file_mode: '0664'
                rsync:
                    args:
                        - '--verbose'
                        - '--archive'
                        - '-z'
                    exclude:
                        - .vagrant/
                        - .git/
                    auto: 'true'
                owner: www-data
                group: www-data
        usable_port_range:
            start: 10200
            stop: 10500
        post_up_message: ''
    ssh:
        host: 'false'
        port: 'false'
        private_key_path: 'false'
        username: vagrant
        guest_port: 'false'
        keep_alive: '1'
        forward_agent: 'false'
        forward_x11: 'false'
        shell: 'bash -l'
        insert_key: 'false'
    vagrant:
        host: detect
    proxy:
        http: ''
        https: ''
        ftp: ''
        no_proxy: ''
server:
    install: '1'
    packages:
        - vim
users_groups:
    install: '1'
    groups: {  }
    users: {  }
locale:
    install: '1'
    settings:
        default_locale: en_US.UTF-8
        locales:
            - en_GB.UTF-8
            - en_US.UTF-8
        timezone: UTC
firewall:
    install: '1'
    rules: {  }
cron:
    install: '1'
    jobs: {  }
nginx:
    install: '1'
    settings:
        version: present
        default_vhost: 1
        proxy_buffers: '4 256k'
        proxy_buffer_size: 128k
        proxy_connect_timeout: 600s
        proxy_send_timeout: 600s
        proxy_read_timeout: 600s
        names_hash_bucket_size: 128
    upstreams: {  }
    vhosts:
        nxv_74ybirqpo6y6:
            server_name: workspace.dev
            www_root: /var/www/workspace
            listen_port: '80'
            client_max_body_size: 1m
            ssl: '0'
            ssl_cert: ''
            ssl_key: ''
            ssl_port: '443'
            ssl_protocols: ''
            ssl_ciphers: ''
            rewrite_to_https: '1'
            spdy: '1'
            locations:
                nxvl_8z3jl4fqoihu:
                    www_root: ''
                    location: /
                    index_files:
                        - index.html
                        - index.htm
                        - index.php
                    try_files:
                        - $uri
                        - $uri/
                        - /index.php$is_args$args
                    fastcgi: ''
                    fastcgi_index: ''
                    fastcgi_split_path: ''
                    proxy: ''
                    proxy_redirect: ''
                nxvl_v3elxlm2ee8t:
                    www_root: ''
                    location: '~ .php$'
                    try_files:
                        - $uri
                        - $uri/
                        - /index.php$is_args$args
                    fastcgi: '127.0.0.1:9000'
                    fastcgi_index: index.php
                    fastcgi_split_path: '^(.+.php)(/.*)$'
                    fast_cgi_params_extra:
                        - 'SCRIPT_FILENAME $request_filename'
                        - 'APP_ENV dev'
                    set:
                        - '$path_info $fastcgi_path_info'
                    proxy: ''
                    proxy_redirect: ''
    proxies: {  }
apache:
    install: '0'
    settings:
        version: 2.4
        user: www-data
        group: www-data
        default_vhost: true
        manage_user: false
        manage_group: false
        sendfile: 0
    modules:
        - proxy_fcgi
        - rewrite
    vhosts:
        av_4infpibvguio:
            servername: awesome.dev
            serveraliases:
                - www.awesome.dev
            docroot: /var/www/awesome
            port: '80'
            setenv:
                - 'APP_ENV dev'
            setenvif:
                - 'Authorization "(.*)" HTTP_AUTHORIZATION=$1'
            custom_fragment: ''
            ssl: '0'
            ssl_cert: ''
            ssl_key: ''
            ssl_chain: ''
            ssl_certs_dir: ''
            ssl_protocol: ''
            ssl_cipher: ''
            directories:
                avd_b11z3wfwne08:
                    path: /var/www/awesome
                    options:
                        - Indexes
                        - FollowSymlinks
                        - MultiViews
                    allow_override:
                        - All
                    require:
                        - 'all granted'
                    custom_fragment: ''
                    files_match:
                        avdfm_hvzzj66xcvle:
                            path: .php$
                            sethandler: 'proxy:fcgi://127.0.0.1:9000'
                            custom_fragment: ''
                            provider: filesmatch
                    provider: directory
letsencrypt:
    install: '1'
    settings:
        email: ''
    domains: {  }
php:
    install: '1'
    settings:
        version: '7.0'
    modules:
        php:
            - cli
            - intl
            - xml
        pear: {  }
        pecl: {  }
    ini:
        display_errors: 'On'
        error_reporting: '-1'
        session.save_path: /var/lib/php/session
        date.timezone: UTC
    fpm_ini:
        error_log: /var/log/php-fpm.log
    fpm_pools:
        phpfp_mbsmnwlxru02:
            ini:
                prefix: www
                listen: '127.0.0.1:9000'
                security.limit_extensions: .php
                user: www-user
                group: www-data
    composer: '1'
    composer_home: ''
xdebug:
    install: '0'
    settings:
        xdebug.default_enable: '0'
        xdebug.remote_autostart: '0'
        xdebug.remote_connect_back: '0'
        xdebug.remote_enable: '0'
        xdebug.remote_handler: dbgp
        xdebug.remote_port: '9000'
blackfire:
    install: '0'
    settings:
        server_id: ''
        server_token: ''
        agent:
            http_proxy: ''
            https_proxy: ''
            log_file: stderr
            log_level: '1'
        php:
            agent_timeout: '0.25'
            log_file: ''
            log_level: '1'
xhprof:
    install: '0'
wpcli:
    install: '0'
    version: v0.24.1
drush:
    install: '0'
    version: 8.0.5
ruby:
    install: '1'
    versions:
        rv_p3peyopuq3qe:
            default: '1'
            bundler: '1'
            version: 2.3.1
            gems:
                - deep_merge@1.0.1
                - activesupport@4.2.6
                - vine@0.2
python:
    install: '1'
    packages: {  }
    versions: {  }
nodejs:
    install: '1'
    settings:
        version: '6'
    npm_packages: {  }
hhvm:
    install: '0'
    composer: '1'
    composer_home: ''
    settings: {  }
    server_ini:
        hhvm.server.host: 127.0.0.1
        hhvm.server.port: '9000'
        hhvm.log.use_log_file: '1'
        hhvm.log.file: /var/log/hhvm/error.log
    php_ini:
        display_errors: 'On'
        error_reporting: '-1'
        date.timezone: UTC
mariadb:
    install: '0'
    settings:
        version: '10.1'
        root_password: '123'
        override_options: {  }
    adminer: 0
    users:
        mariadbnu_pc6gjoy99feb:
            name: dbuser
            password: '123'
    databases:
        mariadbnd_wt6ozsihg8us:
            name: dbname
            sql: ''
    grants:
        mariadbng_nc5i0ukkwapg:
            user: dbuser
            table: '*.*'
            privileges:
                - ALL
mysql:
    install: '1'
    settings:
        version: '5.7'
        root_password: '123'
        override_options: {  }
    adminer: 0
    users:
        mysqlnu_mqqy0asimbr1:
            name: dbuser
            password: '123'
    databases:
        mysqlnd_99t2ic6cge0q:
            name: dbname
            sql: ''
    grants:
        mysqlng_imc2gpk71d6v:
            user: dbuser
            table: '*.*'
            privileges:
                - ALL
postgresql:
    install: '0'
    settings:
        global:
            encoding: UTF8
            version: '9.6'
        server:
            postgres_password: '123'
    databases: {  }
    users: {  }
    grants: {  }
    adminer: 0
mongodb:
    install: '0'
    settings:
        bind_ip: 127.0.0.1
        port: '27017'
    globals:
        version: 2.6.0
    databases: {  }
redis:
    install: '0'
    settings:
        port: '6379'
sqlite:
    install: '0'
    adminer: 0
    databases: {  }
mailhog:
    install: '0'
    settings:
        smtp_ip: 0.0.0.0
        smtp_port: 1025
        http_ip: 0.0.0.0
        http_port: '8025'
        path: /usr/local/bin/mailhog
beanstalkd:
    install: '0'
    settings:
        listenaddress: 0.0.0.0
        listenport: '11300'
        maxjobsize: '65535'
        maxconnections: '1024'
        binlogdir: /var/lib/beanstalkd/binlog
        binlogfsync: null
        binlogsize: '10485760'
    beanstalk_console: 0
rabbitmq:
    install: '0'
    settings:
        port: '5672'
    users: {  }
    vhosts: {  }
    plugins: {  }
elastic_search:
    install: '0'
    settings:
        version: 2.3.1
        java_install: true
    instances:
        esi_tu0viqar5x3i:
            name: es-01
solr:
    install: '0'
    settings:
        version: 5.5.2
        port: '8984'

Edited January 14, 2017 by Freid001

Источник

Troubleshooting

How to access the Application Logs?

Oops! An Error Occurred

The server returned a «500 Internal Server Error»

The server returned a «404 Not Found»

Comments

!!! Sorry for may very bad english !!!

This comment has been minimized.

Recommended Posts

Stack Trace

Stack Trace (Plain Text)

Share this post

Link to post

Share on other sites

Share this post

Link to post

Share on other sites

Share this post

Link to post

Share on other sites

Share this post

Link to post

Share on other sites

Share this post

Link to post

Share on other sites

Share this post

Link to post

Share on other sites

Create an account or sign in to comment

Sign in