# Getting 502 Bad Gateaway

**URL:** <https://help.nextcloud.com/t/getting-502-bad-gateaway/93906>\
**Category:** ℹ️ Support\
**Tags:** nginx, archlinux\
**Created:** [October 4, 2020, 12:42am UTC](https://help.nextcloud.com/t/getting-502-bad-gateaway/93906 "2020-10-04T00:42:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![TornaxO7](https://help.nextcloud.com/letter_avatar/tornaxo7/32/6_22734026db12803ebb3e059622ac3534.png) [@TornaxO7](https://help.nextcloud.com/u/TornaxO7)\
**Post date:** [October 4, 2020, 12:42am UTC](https://help.nextcloud.com/t/getting-502-bad-gateaway/93906/1 "2020-10-04T00:42:36Z")

</div>

Hello guys! Nextcloud is frustrating me. So my OS is `Arch Linux` and this is in my `/etc/nginx/nginx.conf`:

```nginx

user http;
worker_processes 1;

#error_log logs/error.log;
#error_log logs/error.log notice;
#error_log logs/error.log info;

#pid logs/nginx.pid;

events {
    worker_connections 1024;
}

http {
    upstream php-handler {
        #server 127.0.0.1:9000;
        server unix:/var/run/php/php-fpm.sock;
    }
    
    server {
        listen 80;
        listen [::]:80;
        server_name localhost;
    
        # Enforce HTTPS
        return 301 https://$server_name$request_uri;
    }
    
    server {
        listen 443 ssl http2;
        listen [::]:443 ssl http2;
        server_name localhost;
    
        # Use Mozilla's guidelines for SSL/TLS settings
        # https://mozilla.github.io/server-side-tls/ssl-config-generator/
        ssl_certificate /nextcloud/certification/server.crt;
        ssl_certificate_key /nextcloud/certification/server.key;
    
        # HSTS settings
        # WARNING: Only add the preload option once you read about
        # the consequences in https://hstspreload.org/. This option
        # will add the domain to a hardcoded list that is shipped
        # in all major browsers and getting removed from this list
        # could take several months.
        #add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;" always;
    
        # set max upload size
        client_max_body_size 512M;
        fastcgi_buffers 64 4K;
    
        # Enable gzip but do not remove ETag headers
        gzip on;
        gzip_vary on;
        gzip_comp_level 4;
        gzip_min_length 256;
        gzip_proxied expired no-cache no-store private no_last_modified no_etag auth;
        gzip_types application/atom+xml application/javascript application/json application/ld+json application/manifest+json application/rss+xml application/vnd.geo+json application/vnd.ms-fontobject application/x-font-ttf application/x-web-app-manifest+json application/xhtml+xml application/xml font/opentype image/bmp image/svg+xml image/x-icon text/cache-manifest text/css text/plain text/vcard text/vnd.rim.location.xloc text/vtt text/x-component text/x-cross-domain-policy;
    
        # Pagespeed is not supported by Nextcloud, so if your server is built
        # with the `ngx_pagespeed` module, uncomment this line to disable it.
        #pagespeed off;
    
        # HTTP response headers borrowed from Nextcloud `.htaccess`
        add_header Referrer-Policy "no-referrer" always;
        add_header X-Content-Type-Options "nosniff" always;
        add_header X-Download-Options "noopen" always;
        add_header X-Frame-Options "SAMEORIGIN" always;
        add_header X-Permitted-Cross-Domain-Policies "none" always;
        add_header X-Robots-Tag "none" always;
        add_header X-XSS-Protection "1; mode=block" always;
    
        # Remove X-Powered-By, which is an information leak
        fastcgi_hide_header X-Powered-By;
    
        # Path to the root of your installation
        root /usr/share/webapps/nextcloud;
    
        # Specify how to handle directories -- specifying `/index.php$request_uri`
        # here as the fallback means that Nginx always exhibits the desired behaviour
        # when a client requests a path that corresponds to a directory that exists
        # on the server. In particular, if that directory contains an index.php file,
        # that file is correctly served; if it doesn't, then the request is passed to
        # the front-end controller. This consistent behaviour means that we don't need
        # to specify custom rules for certain paths (e.g. images and other assets,
        # `/updater`, `/ocm-provider`, `/ocs-provider`), and thus
        # `try_files $uri $uri/ /index.php$request_uri`
        # always provides the desired behaviour.
        index index.php index.html /index.php$request_uri;
    
        # Default Cache-Control policy
        expires 1m;
    
        # Rule borrowed from `.htaccess` to handle Microsoft DAV clients
        location = / {
            if ( $http_user_agent ~ ^DavClnt ) {
                return 302 /remote.php/webdav/$is_args$args;
            }
        }
    
        location = /robots.txt {
            allow all;
            log_not_found off;
            access_log off;
        }
    
        # Make a regex exception for `/.well-known` so that clients can still
        # access it despite the existence of the regex rule
        # `location ~ /(\.|autotest|...)` which would otherwise handle requests
        # for `/.well-known`.
        location ^~ /.well-known {
            # The following 6 rules are borrowed from `.htaccess`
    
            rewrite ^/\.well-known/host-meta\.json /public.php?service=host-meta-json last;
            rewrite ^/\.well-known/host-meta /public.php?service=host-meta last;
            rewrite ^/\.well-known/webfinger /public.php?service=webfinger last;
            rewrite ^/\.well-known/nodeinfo /public.php?service=nodeinfo last;
    
            location = /.well-known/carddav { return 301 /remote.php/dav/; }
            location = /.well-known/caldav { return 301 /remote.php/dav/; }
    
            try_files $uri $uri/ =404;
        }
    
        # Rules borrowed from `.htaccess` to hide certain paths from clients
        location ~ ^/(?:build|tests|config|lib|3rdparty|templates|data)(?:$|/) { return 404; }
        location ~ ^/(?:\.|autotest|occ|issue|indie|db_|console) { return 404; }
    
        # Ensure this block, which passes PHP files to the PHP process, is above the blocks
        # which handle static assets (as seen below). If this block is not declared first,
        # then Nginx will encounter an infinite rewriting loop when it prepends `/index.php`
        # to the URI, resulting in a HTTP 500 error response.
        location ~ \.php(?:$|/) {
            fastcgi_split_path_info ^(.+?\.php)(/.*)$;
            set $path_info $fastcgi_path_info;
    
            try_files $fastcgi_script_name =404;
    
            include fastcgi_params;
            fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
            fastcgi_param PATH_INFO $path_info;
            fastcgi_param HTTPS on;
    
            fastcgi_param modHeadersAvailable true; # Avoid sending the security headers twice
            fastcgi_param front_controller_active true; # Enable pretty urls
            fastcgi_pass php-handler;
    
            fastcgi_intercept_errors on;
            fastcgi_request_buffering off;
        }
    
        location ~ \.(?:css|js|svg|gif)$ {
            try_files $uri /index.php$request_uri;
            expires 6M; # Cache-Control policy borrowed from `.htaccess`
            access_log off; # Optional: Don't log access to assets
        }
    
        location ~ \.woff2?$ {
            try_files $uri /index.php$request_uri;
            expires 7d; # Cache-Control policy borrowed from `.htaccess`
            access_log off; # Optional: Don't log access to assets
        }
    
        location / {
            try_files $uri $uri/ /index.php$request_uri;
        }
    }
}

```

This might be interesting. If I type `localhost` in my browser than this pops up in `sudo systemctl status nginx.service`:

```auto
Oct 04 02:39:52 TORNAX-ARCH nginx[36569]: 2020/10/04 02:39:52 [crit] 36569#36569: *2 connect() to unix:/var/run/php/php-fpm.sock failed (2: No such file or directory) while connecting to u>
Oct 04 02:39:52 TORNAX-ARCH nginx[36569]: 2020/10/04 02:39:52 [crit] 36569#36569: *2 connect() to unix:/var/run/php/php-fpm.sock failed (2: No such file or directory) while connecting to u>

```

But if I type `ls /var/run/php-fpm | grep php-fpm` than I can see the `php-fpm.sock` file.  
Every help is appreciated!

---

<div class="post-metadata">

**Author:** ![system](https://help.nextcloud.com/user_avatar/help.nextcloud.com/system/32/29333_2.png) [@system](https://help.nextcloud.com/u/system)\
**Post date:** [September 23, 2024, 4:40pm UTC](https://help.nextcloud.com/t/getting-502-bad-gateaway/93906/2 "2024-09-23T16:40:49Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [December 12, 2024, 10:05am UTC](https://help.nextcloud.com/t/getting-502-bad-gateaway/93906/3 "2024-12-12T10:05:56Z")

</div>


