http – Nginx showing 504 Gateway timed out when uploading large files

I have a simple PHP file upload script that uploads a file. The server consists of 1 nginx reverse proxy and another nginx server (upstream). The problem is that when I try to upload very large files ~ 2GB then I get an error:

504 Gateway Time-out

Here is my reverse proxy configuration:

server {
    listen 80;
    
    server_name upload.mycloudhost.com;

    proxy_buffer_size 1024k;
    proxy_buffers 4 1024k;
    proxy_busy_buffers_size 1024k;
    proxy_connect_timeout       600;
    proxy_send_timeout          600;
    proxy_read_timeout          600;
    send_timeout                600;
    client_body_timeout         600;
    client_header_timeout       600;
    keepalive_timeout           600;
    uwsgi_read_timeout          600;

    location / {
        proxy_set_header X-Real-IP  $remote_addr;
        proxy_set_header X-Forwarded-For $remote_addr;
        proxy_set_header Host $host;
        proxy_pass http://localhost:13670;
    }
}

And here is the other nginx server (upstream):

server {
    listen 80;
    
    server_name upload.mycloudhost.com;

    client_max_body_size 80G;
    proxy_buffer_size 1024k;
    proxy_buffers 4 1024k;
    proxy_busy_buffers_size 1024k;
    proxy_connect_timeout       600;
    proxy_send_timeout          600;
    proxy_read_timeout          600;
    send_timeout                600;
    client_body_timeout         600;
    client_header_timeout       600;
    keepalive_timeout           600;
    uwsgi_read_timeout          600;

    root /var/www/mycloudhost;
    index index.php index.html index.htm index.nginx-debian.html;

    location ~ .php$ {
        try_files $uri =404;
        fastcgi_split_path_info ^(.+.php)(/.+)$;
        fastcgi_pass php:9000;
        fastcgi_index index.php;
        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        fastcgi_param PATH_INFO $fastcgi_path_info;
    }

    location / {
        try_files $uri $uri/ =404;
    }
}

Error : Return – SockError: Connection timed out — 👉 GSA SEO and Marketing Forum 👈

Hello, i get this error and can not fix. 

2021-02-15 22:14: *@worried.watchonlineshops.com: POP3 Login failed – SockError: Non authoritative – host not found
2021-02-15 22:12: *@vision.katasumber.com: POP3 Login failed – SockError: Connection timed out
2021-02-15 22:10: *@writing.kategoriblog.com: POP3 Login failed – SockError: Connection timed out

What does it mean ?

wifi – MacBook Pro crash – Sleep transition timed out AppleBCMWLANCore

My MacBook Pro 16 (2019) keeps crashing either when going to sleep or when waking up from sleep, when the power is disconnected and WiFi is on. Seems to be due to com.apple.driver.AppleBCMWLANCore.

I’ve confirmed that it does not crash when the power cable is kept plugged in, or when WiFi is turned off before closing the lid.

It is on macOS 10.15.7 (cannot update yet due to compatibility with some required software).

Is there a fix? I’ve tried NVRAM and SMC reset.

The top of the crash logs:

panic(cpu 0 caller 0xffffff801a68ef7c): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.driver.AppleBCMWLANCore. Thread 0x5460d.

Full crash logs: https://pastebin.com/JaP4GNbz

command line – pip gets “read timed out” by unusual reason

Command pip install future returns:

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)",)': /simple/future/

Five times, and then No matching distribution found.

I have tried:

  1. this command with flag --default-timeout=1000 (and 100, of course) doesn’t help. It doesn’t relate to the throughput of my Internet connection.

  2. check connection using nmap -p 443 pypi.org at the same time returns a valid latency:

     Starting Nmap 7.60 ( https://nmap.org ) at 2021-01-17 22:02 IST
     Nmap scan report for pypi.org (151.101.128.223)
     Host is up (0.067s latency).
     Other addresses for pypi.org (not scanned): ...        
     PORT    STATE SERVICE
     443/tcp open  https        
     Nmap done: 1 IP address (1 host up) scanned in 1.43 seconds
    
  3. run command with sudo — same result, of course, but my setup allowed to install without sudo.

  4. I tried to check it by wireshark. I see several lines, each of them with (RST) – reset, connection termination.

    Example line:

     7807    476.831742090   2a00:...:a9e3   2a04:4e42:400::223  TCP 76  36918 → 443 (RST) Seq=1 Win=0 Len=0
    

And I have no idea why was it reset.

  1. It works from another computer from the same network.

Can you suggest any way how can I resolve my issue, and be able to use pip?
The installation process have to be automated, to I can’t resolve it by manually download of sources & install them.

displays – Does incorrectly timed horizontal and vertical sync damage a monitor?

Recently, I got the urge to hijack a VGA connection with an Arduino so that I can draw on the screen.

However, I have heard from multiple sources including Ben Eater and posts from retrocomputing.stackexchange.com that it is possible to fry a CRT if you incorrectly time the horizontal and vertical sync. Does this principle also apply to modern flatscreen displays? I have not tested my theory yet as I don’t want to risk damaging any of my monitors.

hostname – Ping server remotely timed out

I recently setup local Ubuntu server to host VS Code and NGINX servers which work fine on codeserver (hostname) and can ping the hostname and IP address remotely. The problem I am facing is that I cannot ping new host created such as project.codeserver or codeserver/project remotely but can ping them while on the server.

In etc/hosts I have typed this 192.168.1.235 codeserver project.codeserver. I also turn off the UFW and same result appear so I think it something else that preventing me to ping the secondary host name.

Any chance someone point me the direction to how can I ping the secondary host remotely?

lightning network – Problem with the first Initialization of my LN node, dial tcp my-external-ip:9735: connect: connection timed out

Background

I was following 402 Payment Required’s LN video over here (https://www.youtube.com/watch?v=q0siLF9zmWo) and everything was good so far, until the moment of the first Initialization of my LN node, I got an (dial tcp my-external-ip:9735: connect: connection timed out) error.

I was starting the Initialization by the following way

lnd –externalip=X.X.X.X

And I’ve my lnd configuration file with the following attributes

alias=
debuglevel=debug
bitcoin.active=1
bitcoin.mainnet=1
bitcoin.node=bitcoind

I created the file (before) I started the Initialization.

Your environment

version of lnd: I don't know, I guess it's the latest version.
which operating system (uname -a on *Nix): Ubuntu 18.04
version of btcd, bitcoind, or other backend: bitcoind 0.19.1
any other relevant environment details: My Ubuntu is running on a VM machine with a (bridged) internet connection

Steps to reproduce

I don’t know how to reproduce the problem but here is a log with my issue

2020-08-14 20:33:16.008 (INF) BTCN: Server listening on (::):9735

2020-08-14 20:33:16.009 (INF) SRVR: Initializing peer network bootstrappers!

2020-08-14 20:33:16.009 (INF) SRVR: Creating DNS peer bootstrapper with seeds: ((nodes.lightning.directory soa.nodes.lightning.directory) (lseed.bitcoinstats.com ))

2020-08-14 20:33:16.010 (INF) DISC: Attempting to bootstrap with: Authenticated Channel Graph

2020-08-14 20:33:16.022 (INF) DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: ((nodes.lightning.directory soa.nodes.lightning.directory) (lseed.bitcoinstats.com ))

2020-08-14 20:33:16.426 (INF) DISC: Obtained 1 addrs to bootstrap network with

2020-08-14 20:33:19.428 (DBG) SRVR: Waiting 2s before trying to locate bootstrap peers (attempt #1)

2020-08-14 20:33:21.428 (INF) DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: ((nodes.lightning.directory soa.nodes.lightning.directory) (lseed.bitcoinstats.com ))

2020-08-14 20:33:21.463 (INF) DISC: Attempting to bootstrap with: Authenticated Channel Graph

2020-08-14 20:33:21.464 (ERR) SRVR: Unable to retrieve initial bootstrap peers: no addresses found

2020-08-14 20:33:21.464 (DBG) SRVR: Waiting 4s before trying to locate bootstrap peers (attempt #2)

2020-08-14 20:33:25.464 (INF) DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: ((nodes.lightning.directory soa.nodes.lightning.directory) (lseed.bitcoinstats.com ))

2020-08-14 20:33:25.504 (INF) DISC: Attempting to bootstrap with: Authenticated Channel Graph

2020-08-14 20:33:25.504 (ERR) SRVR: Unable to retrieve initial bootstrap peers: no addresses found

2020-08-14 20:33:25.504 (DBG) SRVR: Waiting 8s before trying to locate bootstrap peers (attempt #3)

2020-08-14 20:33:33.504 (INF) DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed:
((nodes.lightning.directory soa.nodes.lightning.directory) (lseed.bitcoinstats.com ))

2020-08-14 20:33:33.539 (INF) DISC: Attempting to bootstrap with: Authenticated Channel Graph

2020-08-14 20:33:33.539 (ERR) SRVR: Unable to retrieve initial bootstrap peers: no addresses found

2020-08-14 20:33:33.539 (DBG) SRVR: Waiting 16s before trying to locate bootstrap peers (attempt #4)

2020-08-14 20:33:49.540 (INF) DISC: Attempting to bootstrap with: Authenticated Channel Graph

2020-08-14 20:33:49.540 (INF) DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: ((nodes.lightning.directory soa.nodes.lightning.directory) (lseed.bitcoinstats.com ))

2020-08-14 20:33:49.578 (ERR) SRVR: Unable to retrieve initial bootstrap peers: no addresses found

2020-08-14 20:33:49.578 (DBG) SRVR: Waiting 32s before trying to locate bootstrap peers (attempt #5)

2020-08-14 20:34:21.579 (INF) DISC: Attempting to bootstrap with: Authenticated Channel Graph

2020-08-14 20:34:21.580 (INF) DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: ((nodes.lightning.directory soa.nodes.lightning.directory) (lseed.bitcoinstats.com ))

2020-08-14 20:34:21.735 (ERR) SRVR: Unable to retrieve initial bootstrap peers: no addresses found

2020-08-14 20:34:21.735 (DBG) SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #6)

2020-08-14 20:35:21.736 (INF) DISC: Attempting to bootstrap with: Authenticated Channel Graph

2020-08-14 20:35:21.736 (INF) DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: ((nodes.lightning.directory soa.nodes.lightning.directory) (lseed.bitcoinstats.com ))

2020-08-14 20:35:22.280 (ERR) SRVR: Unable to retrieve initial bootstrap peers: no addresses found

2020-08-14 20:35:22.280 (DBG) SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #7)

2020-08-14 20:35:27.316 (ERR) SRVR: Unable to connect to ##################################################################@my-external-ip:9735: dial tcp my-external-ip:9735: connect: connection timed out

2020-08-14 20:36:22.280 (INF) DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed:
((nodes.lightning.directory soa.nodes.lightning.directory) (lseed.bitcoinstats.com ))

2020-08-14 20:36:22.347 (INF) CRTR: Pruning channel graph using block 0000000000000000000f09423cef42338b27f29244a99deed77411cf2e6edb57 (height=643720)

2020-08-14 20:36:22.349 (INF) CRTR: Block 0000000000000000000f09423cef42338b27f29244a99deed77411cf2e6edb57 (height=643720) closed 0 channels

2020-08-14 20:36:22.461 (DBG) NTFN: Filtering 3178 txns for 0 spend requests at height 643720

2020-08-14 20:36:22.523 (INF) NTFN: New block: height=643720, sha=0000000000000000000f09423cef42338b27f29244a99deed77411cf2e6edb57

2020-08-14 20:36:22.523 (DBG) SWPR: New block: height=643720, sha=0000000000000000000f09423cef42338b27f29244a99deed77411cf2e6edb57

2020-08-14 20:36:22.523 (INF) UTXN: Attempting to graduate height=643720: num_kids=0, num_babies=0

2020-08-14 20:36:22.524 (DBG) DISC: New block: height=643720, hash=0000000000000000000f09423cef42338b27f29244a99deed77411cf2e6edb57

2020-08-14 20:36:22.757 (INF) DISC: Attempting to bootstrap with: Authenticated Channel Graph

2020-08-14 20:36:22.758 (ERR) SRVR: Unable to retrieve initial bootstrap peers: no addresses found

2020-08-14 20:36:22.758 (DBG) SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #8)

I tried dig nodes.lightning.directory and got the following output

; <<>> DiG 9.11.3-1ubuntu1.12-Ubuntu <<>> nodes.lightning.directory

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48349

;; flags: qr rd ra; QUERY: 1, ANSWER: 25, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 65494

;; QUESTION SECTION:

;nodes.lightning.directory. IN A

;; ANSWER SECTION:

nodes.lightning.directory. 60 IN A 93.46.54.4

nodes.lightning.directory. 60 IN A 82.1.254.100

nodes.lightning.directory. 60 IN A 83.162.151.227

nodes.lightning.directory. 60 IN A 163.158.202.112

nodes.lightning.directory. 60 IN A 212.47.254.6

nodes.lightning.directory. 60 IN A 3.12.163.140

nodes.lightning.directory. 60 IN A 178.128.165.102

nodes.lightning.directory. 60 IN A 51.83.41.129

nodes.lightning.directory. 60 IN A 193.194.163.53

nodes.lightning.directory. 60 IN A 35.229.93.213

nodes.lightning.directory. 60 IN A 52.38.99.14

nodes.lightning.directory. 60 IN A 3.16.193.211

nodes.lightning.directory. 60 IN A 73.147.115.80

nodes.lightning.directory. 60 IN A 176.122.101.230

nodes.lightning.directory. 60 IN A 173.249.48.168

nodes.lightning.directory. 60 IN A 18.223.138.245

nodes.lightning.directory. 60 IN A 203.118.186.226

nodes.lightning.directory. 60 IN A 104.248.111.88

nodes.lightning.directory. 60 IN A 46.59.13.35

nodes.lightning.directory. 60 IN A 185.228.141.6

nodes.lightning.directory. 60 IN A 98.210.161.137

nodes.lightning.directory. 60 IN A 86.176.78.2

nodes.lightning.directory. 60 IN A 152.32.173.177

nodes.lightning.directory. 60 IN A 176.74.136.237

nodes.lightning.directory. 60 IN A 45.77.156.146

;; Query time: 154 msec

;; SERVER: 127.0.0.53#53(127.0.0.53)

;; WHEN: Fri Aug 14 23:13:30 EET 2020

;; MSG SIZE rcvd: 454

Expected behavior

I expected the Initialization would work normally without any issues.

Actual behavior

The first Initialization of the LN node didn’t happen, stuck in the loop of trying to locate bootstrap peers

terminal – Mount and repair disk not recognized (Timed out waiting)

I’ve a 525 GB Crucial SSD that I can’t mount. It appears only greyed out on Disk Utility but not in Finder or Desktop.

Here’s the disk description by diskutil list

/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *525.1 GB   disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS SSD500                  524.1 GB   disk2s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk2s3

diskutil verifyDisk /dev/disk2 and diskutil repairDisk /dev/disk2 say The partition map appears to be OK

  1. I tried to mount the disk with diskutil mount /dev/disk2 but I got Volume on disk2 timed out waiting to mount

  2. I tried using diskutil mount readOnly /dev/disk2 but I also got Volume on disk2 timed out waiting to mount

  3. I tried to force mount the disk with a specific filesystem using mount force -t Apple_HFS /dev/disk2 but nothing.

At the end I wrote diskutil repairVolume /dev/disk2 but I got this error that I didn’t know:

Error starting file system repair for disk2: Invalid request (-69886)

Here’s a gpt output from sudo gpt -r show /dev/disk2 if needed:

start        size  index  contents
           0           1         PMBR
           1           1         Pri GPT header
           2          32         Pri GPT table
          34           6         
          40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      409640  1023669408      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  1024079048      262144         
  1024341192     1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
  1025610728           7         
  1025610735          32         Sec GPT table
  1025610767           1         Sec GPT header

There’re some alphanumeric codes wrongs? What could I do?

I think that the problem is on the disk2s2 Volume (Apple_HFS SSD500)..maybe enter in Safe Mode and use fsck could be useful? Thanks in advance.

applications – Autodialling app that allows timed selection of phone line menu options

I have searched the Google Play store with a number of likely terms to find this, and Googled also, only to find “simplistic” options for auto dialling.

Am trying to get through to a government department that allows call backs, but don’t just want to select the number at a pre-determined interval from the last call (to give their system a chance to clear some of those call backs), something I can relatively easily do myself, it would be most helpful to have dialpad numbers sent down the line at predetermined times once the phone connects, so I don’t have to wait to be able to select each of them.

This seems like it would be the most programmatically simple part of a auto dialler app. Does an app to do this really not exist for Android?

domain name system – connection timed out; no servers could be reached when using dig to query dns in kvm machine

When I am using this command to dig dns in my KVM virtual machine(CentOS 8):

(root@k8sslave1 ~)# dig www.stackoverflow.com

; <<>> DiG 9.11.13-RedHat-9.11.13-3.el8 <<>> www.stackoverflow.com
;; global options: +cmd
;; connection timed out; no servers could be reached

and this is my resolv.conf vim /etc/resolv.conf:

# Generated by NetworkManager
nameserver 114.114.115.115

when I ping IP of internet, it works fine. For exmaple:

(root@k8sslave1 ~)# ping 114.114.115.115
PING 114.114.115.115 (114.114.115.115) 56(84) bytes of data.
64 bytes from 114.114.115.115: icmp_seq=1 ttl=89 time=21.2 ms
64 bytes from 114.114.115.115: icmp_seq=2 ttl=91 time=20.5 ms
64 bytes from 114.114.115.115: icmp_seq=3 ttl=83 time=20.8 ms

without dns resolve, I could not work in the virtual mahcine, I could not access any resource, and could not install software. so where is going wrong? what should I do fix this problem?