Support » Plugin: WP Telegram (Auto Post and Notifications) » Stack LEMP ubuntu: error 500 http_request_failed – cURL error

  • Resolved Danilo

    (@lookiz)


    Hello,

    I installed a lemp stack (nginx) on ubuntu 18.04. installed wordpress but the plugin returns the error test:

    Test Result: Errore: 500 – http_request_failed – cURL error 28: Operation timed out after 20001 milliseconds with 0 bytes received

    how can I solve this problem?

    thanks

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Manzoor Wani

    (@manzoorwanijk)

    A few questions:

    1. When does it happen? During testing or when sending the posts?
    2. Is the message sent to Telegram?
    3. Is your host in Russia or Iran which blocks Telegram?
    Danilo

    (@lookiz)

    during the token bot test
    no the message is not sent
    my datacenter is in Moldova

    Plugin Author Manzoor Wani

    (@manzoorwanijk)

    It seems to be some issue with PHP set up. Do you use a VPS or shared hosting?

    Danilo

    (@lookiz)

    I use a dedicated server, my configuration looks good everything works, Site Health WP is ok no error

    Plugin Author Manzoor Wani

    (@manzoorwanijk)

    If you have command line access to the server, can you please try ping telegram.org and ping api.telegram.org?
    You can send the results to our support on Telegram (@WPTelegramSupport) to have a look.

    here are the ping results

    $ ping telegram.org
    PING telegram.org (149.154.167.99) 56(84) bytes of data.
    From 87.245.213.247 (87.245.213.247) icmp_seq=9 Packet filtered
    From 87.245.213.247 (87.245.213.247) icmp_seq=12 Packet filtered
    ^C
    — telegram.org ping statistics —
    105 packets transmitted, 0 received, +2 errors, 100% packet loss, time 106430ms

    $ ping api.telegram.org
    PING api.telegram.org (149.154.167.220) 56(84) bytes of data.
    64 bytes from 149.154.167.220 (149.154.167.220): icmp_seq=1 ttl=56 time=40.6 ms
    64 bytes from 149.154.167.220 (149.154.167.220): icmp_seq=2 ttl=56 time=40.6 ms
    — api.telegram.org ping statistics —
    37 packets transmitted, 37 received, 0% packet loss, time 36026ms
    rtt min/avg/max/mdev = 40.675/40.834/43.463/0.462 ms

    Plugin Author Manzoor Wani

    (@manzoorwanijk)

    It seems like there is some host in your network route that blocks Telegram. It may be a Russian host, because they block Telegram. You can contact your server provider and ask about requests to api.telegram.org being timed out.

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.