telescope: 502 Bad Gateway when enabled

Hello,

When telescope is enabled, one of the routes in our app gives an nginx 502 bad gateway error. We experience this on a forge server and locally on valet. Without telescope, this route works fine. It is fairly resource intensive, but it does work. Tried (unsuccessfully) to debug this in various ways but haven’t come up with much. Strangely, commenting out everything in the register() method of my app’s TelescopeServiceProvider doesn’t change anything. Toggling the TELESCOPE_ENABLED env variable does fix the issue though.

Nothing goes in the laravel.log file, nothing in the nginx error log, and the php-fpm log only shows:

What else might I try to debug this?

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 23 (5 by maintainers)

Most upvoted comments

Same here. Error 500 when 'enabled' => env('TELESCOPE_ENABLED', true) but everything works fine when disabled. No logs in laraval, nginx, or php. Nginx access logs shows 500. Trying to track down. @TiagoSilvaPereira did you find the culprit yet? Our Laravel setup is API only.

danDanV1 on Dec 24, 2018

@divspace install the mbstring bcmath extensions for your docker php and problem solved.

my dockerfile:

FROM php:7.2.8-fpm-alpine3.7
RUN apk add --no-cache --update --virtual buildDeps autoconf automake make gcc g++\
    && pecl install redis \
    && pecl install xdebug \
    && docker-php-ext-enable redis xdebug \
    && docker-php-ext-install pdo pdo_mysql json mbstring bcmath \
    && docker-php-ext-enable pdo pdo_mysql json mbstring bcmath \
    && apk del buildDeps autoconf automake make gcc g++

danDanV1 on Jan 17, 2019

I have experienced this too, but after fiddling with some PHP extensions that I can’t remember anymore it just started working. On Homestead it worked, when I switched to Docker it did not work, but after I installed some PHP extensions it started working.

mabasic on Dec 29, 2018