Support Euse

Euse

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 16 total)
  • In reply to: Sitemap Error

    Ok, I hope you can fix this issue.

    In reply to: Sitemap Error

    I HAVE DEACTIVATED YOUR SITEMAP and USING THE GOOGLE XML SITEMAP with no errors.

    So basically, the problem is not my hosting, not other plugin I use. Rankmath is the culprit here.

    This is my new sitemap
    https://bitmoneytalk.com/sitemap.xml

    I hope you can fix your sitemap soon.

    In reply to: Sitemap Error

    I am currently migrating my website to another host. I will let you know if I still get the error. Thank you.

    In reply to: Sitemap Error

    Thank you.

    I need to solve this as soon as possible because it’s hurting my SEO now. When I check some keywords I am now on the 2nd page of the search results which before is on the first page. 🙁 🙁 🙁

    In reply to: Sitemap Error

    And this one is the syslog error

    May 5 14:45:01 bitmoneytalk CRON[3556]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
    May 5 14:45:01 bitmoneytalk CRON[3557]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-rrd)
    May 5 14:45:01 bitmoneytalk CRON[3559]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-queue letsencrypt)
    May 5 14:45:01 bitmoneytalk CRON[3558]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-queue backup)
    May 5 14:47:14 bitmoneytalk systemd-resolved[638]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
    May 5 14:48:29 bitmoneytalk systemd[1]: Stopping nginx – high performance web server…
    May 5 14:48:29 bitmoneytalk systemd[1]: Stopped nginx – high performance web server.
    May 5 14:48:29 bitmoneytalk systemd[1]: Starting nginx – high performance web server…
    May 5 14:48:29 bitmoneytalk systemd[1]: Started nginx – high performance web server.
    May 5 14:48:29 bitmoneytalk systemd[1]: Reloading The Apache HTTP Server.
    May 5 14:48:30 bitmoneytalk systemd-resolved[638]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
    May 5 14:48:30 bitmoneytalk apachectl[4996]: AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using bitmoneytalk.com. Set the ‘ServerName’ directive globally to suppress this message
    May 5 14:48:30 bitmoneytalk systemd[1]: Reloaded The Apache HTTP Server.
    May 5 14:48:32 bitmoneytalk systemd[1]: Stopping nginx – high performance web server…
    May 5 14:48:32 bitmoneytalk systemd[1]: Stopped nginx – high performance web server.
    May 5 14:48:32 bitmoneytalk systemd[1]: Starting nginx – high performance web server…
    May 5 14:48:32 bitmoneytalk systemd[1]: Started nginx – high performance web server.
    May 5 14:48:32 bitmoneytalk systemd[1]: Reloading The Apache HTTP Server.
    May 5 14:48:33 bitmoneytalk apachectl[5175]: AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using bitmoneytalk.com. Set the ‘ServerName’ directive globally to suppress this message
    May 5 14:48:33 bitmoneytalk systemd[1]: Reloaded The Apache HTTP Server.
    May 5 14:48:38 bitmoneytalk systemd[1]: Reloading The Apache HTTP Server.
    May 5 14:48:38 bitmoneytalk apachectl[5509]: AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using bitmoneytalk.com. Set the ‘ServerName’ directive globally to suppress this message
    May 5 14:48:38 bitmoneytalk systemd[1]: Reloaded The Apache HTTP Server.
    May 5 14:48:38 bitmoneytalk systemd[1]: Stopping nginx – high performance web server…
    May 5 14:48:38 bitmoneytalk systemd[1]: Stopped nginx – high performance web server.
    May 5 14:48:38 bitmoneytalk systemd[1]: Starting nginx – high performance web server…
    May 5 14:48:38 bitmoneytalk systemd[1]: Started nginx – high performance web server.
    May 5 14:48:39 bitmoneytalk systemd[1]: Reloading The Apache HTTP Server.
    May 5 14:48:39 bitmoneytalk apachectl[5687]: AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using bitmoneytalk.com. Set the ‘ServerName’ directive globally to suppress this message
    May 5 14:48:39 bitmoneytalk systemd[1]: Reloaded The Apache HTTP Server.
    May 5 14:48:39 bitmoneytalk systemd[1]: Stopping nginx – high performance web server…
    May 5 14:48:39 bitmoneytalk systemd[1]: Stopped nginx – high performance web server.
    May 5 14:48:39 bitmoneytalk systemd[1]: Starting nginx – high performance web server…
    May 5 14:48:39 bitmoneytalk systemd[1]: Started nginx – high performance web server.
    May 5 14:48:39 bitmoneytalk systemd[1]: Reloading The Apache HTTP Server.
    May 5 14:48:39 bitmoneytalk apachectl[5782]: AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using bitmoneytalk.com. Set the ‘ServerName’ directive globally to suppress this message
    May 5 14:48:39 bitmoneytalk systemd[1]: Reloaded The Apache HTTP Server.
    May 5 14:48:39 bitmoneytalk systemd[1]: Stopping nginx – high performance web server…
    May 5 14:48:39 bitmoneytalk systemd[1]: Stopped nginx – high performance web server.
    May 5 14:48:39 bitmoneytalk systemd[1]: Starting nginx – high performance web server…
    May 5 14:48:39 bitmoneytalk systemd[1]: Started nginx – high performance web server.
    May 5 14:50:01 bitmoneytalk CRON[6317]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-queue letsencrypt)
    May 5 14:50:01 bitmoneytalk CRON[6319]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-rrd)
    May 5 14:50:01 bitmoneytalk CRON[6318]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-queue backup)
    May 5 14:50:42 bitmoneytalk systemd[1]: Started Session 17 of user root.
    May 5 14:51:03 bitmoneytalk systemd[1]: Started Session 18 of user root.

    In reply to: Sitemap Error

    I’m not sure if this is the log you are looking for.

    [03-May-2020 06:25:02] NOTICE: error log file re-opened
    [04-May-2020 07:44:27] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
    [04-May-2020 09:54:23] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
    [04-May-2020 12:39:04] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
    [04-May-2020 13:47:29] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
    [04-May-2020 14:19:17] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
    [04-May-2020 22:56:17] WARNING: [pool bitmoneytalk.com] child 8490, script ‘//home/admin/web/bitmoneytalk.com/public_html/wp-admin/admin-ajax.php’ (request: “POST /wp-admin/admin-ajax.php”) execution timed out (35.975143 sec), terminating
    [04-May-2020 22:56:17] WARNING: [pool bitmoneytalk.com] child 8490 exited on signal 15 (SIGTERM) after 172.433711 seconds from start
    [04-May-2020 22:56:17] NOTICE: [pool bitmoneytalk.com] child 9126 started
    [04-May-2020 23:54:27] WARNING: [pool bitmoneytalk.com] child 18107, script ‘//home/admin/web/bitmoneytalk.com/public_html/wp-admin/admin-ajax.php’ (request: “POST /wp-admin/admin-ajax.php?action=rocket_database_optimization&nonce=ec6632072e”) execution timed out (35.031766 sec), terminating
    [04-May-2020 23:54:27] WARNING: [pool bitmoneytalk.com] child 18107 exited on signal 15 (SIGTERM) after 618.935757 seconds from start
    [04-May-2020 23:54:27] NOTICE: [pool bitmoneytalk.com] child 19779 started
    [05-May-2020 00:06:53] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
    [05-May-2020 02:59:17] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
    [05-May-2020 06:31:10] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
    [05-May-2020 11:15:18] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
    [05-May-2020 11:26:09] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
    [05-May-2020 13:36:20] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
    [05-May-2020 13:57:17] NOTICE: Terminating …
    [05-May-2020 13:57:17] NOTICE: exiting, bye-bye!
    [05-May-2020 13:57:17] NOTICE: fpm is running, pid 4627
    [05-May-2020 13:57:17] NOTICE: ready to handle connections
    [05-May-2020 13:57:17] NOTICE: systemd monitor interval set to 10000ms
    [05-May-2020 14:09:29] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
    [05-May-2020 14:36:08] NOTICE: Terminating …
    [05-May-2020 14:36:08] NOTICE: exiting, bye-bye!
    [05-May-2020 14:38:58] NOTICE: fpm is running, pid 668
    [05-May-2020 14:38:58] NOTICE: ready to handle connections
    [05-May-2020 14:38:58] NOTICE: systemd monitor interval set to 10000ms

    In reply to: Sitemap Error

    I am using an external cron(easy cron) and disable the wordpress cron. Does it affect that? or there is no connection in any way?

    In reply to: Sitemap Error

    Hi,

    I have two separate server. one for the database and one for the files. I have a dedicated server for the files and a cloud server for the database. I have full root access to all my servers. Could you please tell me what exactly is the issue? I have tried to use the sitemap of jetpack and I don’t have any issue with it.

    So I think it’s not a hosting issue but I think it’s a plugin issue.

    I hope you can help me fix this.

    In reply to: Sitemap Error

    When I make a new post, and then I visit the first post sitemap, I will get that error.

    But when I try to reload and reload the page, it will work fine without errors.

    So what I did is that I have to visit the first post sitemap too often if there are new posts.

    I have that enabled already. It’s not working.

    Hello,

    I have updated the sensitive data as requested. Can you please check further?

    Thank you.

    Hello,

    I have updated the sensitive data as requested. Can you please check further?

    Thank you.

    Hello,

    I have updated the sensitive data as requested. Can you please check further?

    Thank you.

    Hello,

    I have updated the sensitive data as requested. Can you please check further?

    Thank you.

    The developer of wpreview pro has solved the problem. Thank you.

Viewing 15 replies - 1 through 15 (of 16 total)