Skip to main content

sitejetbulder Not all pages of my website my website are published | Help

Comments

13 comments

  • cPRex Jurassic Moderator

    Hey there!  Do you have root access to the server?  Someone with root access to the machine would need ti investigate this issue so they have access to all the logs that are available on the system, but with the details you've posted there isn't enough information to help troubleshoot the problem.

    0
  • Jaap van der linde
    No, I don't have that and Ikoula.com says that the problem is not theirs. What is the best thing I can ask them to do?
    0
  • cPRex Jurassic Moderator

    They would need to check the logs on the server to see if there are any issues with the Sitejet operations.  The logs for publishing Sitejet can be found at 

    /home/USER/logs/publish_timestamp.log

    so you could also check that area through SSH or through File Manager.

    0
  • Jaap van der linde

    Thank you very much for helping me.  I can access logs but do not see the folder: publish_timestamp.log.  This is what I see:  

    • proxy_error_log.7.gz      2024-10-2 12:55              457 B    rw- r-- r--            root       root      
    •                 proxy_error_log.6.gz     2024-10-3 08:32              20 B       rw- r-- r--            root       root              
    •                 proxy_error_log.5.gz     2024-10-4 08:29              20 B       rw- r-- r--            root       root              
    •                 proxy_error_log.4.gz     2024-10-5 20:19              589 B    rw- r-- r--            root       root              
    •                 proxy_error_log.3.gz     2024-10-6 08:35              20 B       rw- r-- r--            root       root              
    •                 proxy_error_log.2.gz     2024-10-8 00:59              748 B    rw- r-- r--            root       root              
    •                 proxy_error_log.1.gz     2024-10-9 00:31              548 B    rw- r-- r--            root       root              
    •                 proxy_error_log              2024-10-9 17:03              352.9 KB             rw- r-- r--            root               root      
    •                 proxy_access_ssl_log    2024-10-9 17:14              270.3 KB             rw- r-- r--            root               root      
    •                 proxy_access_log           2024-10-9 12:06              457 B    rw- r-- r--            root       root              
    •                 error_log.7.gz   2024-10-2 12:55              1.8 KB   rw- r-- r--            root       root      
    •                 error_log.6.gz   2024-10-3 16:27              1013 B  rw- r-- r--            root       root      
    •                 error_log.5.gz   2024-10-4 08:29              20 B       rw- r-- r--            root       root      
    •                 error_log.4.gz   2024-10-6 04:52              1.4 KB   rw- r-- r--            root       root      
    •                 error_log.3.gz   2024-10-6 09:14              459 B    rw- r-- r--            root       root      
    •                 error_log.2.gz   2024-10-8 00:53              4.3 KB   rw- r-- r--            root       root      
    •                 error_log.1.gz   2024-10-8 23:07              3.4 KB   rw- r-- r--            root       root      
    •                 error_log           2024-10-9 16:08              1.3 KB   rw- r-- r--            root       root      
    •                 access_ssl_log.webstat 2024-10-9 10:15              0 B         rw- r-- r--            root       root              
    •                 access_ssl_log.stat        2024-10-9 09:53              109.8 KB             rw- r-- r--            root               root      
    •                 access_ssl_log.processed.7.gz   2024-10-3 08:32              49.9 KB rw- r-- r--            root               root      
    •                 access_ssl_log.processed.6.gz   2024-10-4 08:28              133.1 KB             rw- r-- r--               root       root      
    •                 access_ssl_log.processed.5.gz   2024-10-5 08:28              57.8 KB rw- r-- r--            root               root      
    •                 access_ssl_log.processed.4.gz   2024-10-6 08:35              74.7 KB rw- r-- r--            root               root      
    •                 access_ssl_log.processed.3.gz   2024-10-7 08:26              38.6 KB rw- r-- r--            root               root      
    •                 access_ssl_log.processed.2.gz   2024-10-8 01:24              63.8 KB rw- r-- r--            root               root      
    •                 access_ssl_log.processed.1.gz   2024-10-9 01:50              50.2 KB rw- r-- r--            root               root      
    •                 access_ssl_log.processed            2024-10-9 08:39              369.3 KB             rw- r-- r--               root       root      
    •                 access_ssl_log  2024-10-9 16:14              76.2 KB rw- r-- r--            root       root      
    •                 access_log.webstat       2024-10-9 10:15              0 B         rw- r-- r--            root       root              
    •                 access_log.processed.7.gz          2024-10-3 08:32              379 B    rw- r-- r--            root               root      
    •                 access_log.processed.6.gz          2024-10-4 08:28              845 B    rw- r-- r--            root               root      
    •                 access_log.processed.5.gz          2024-10-5 08:28              797 B    rw- r-- r--            root               root      
    •                 access_log.processed.4.gz          2024-10-6 08:35              938 B    rw- r-- r--            root               root      
    •                 access_log.processed.3.gz          2024-10-7 08:26              1.1 KB   rw- r-- r--            root               root      
    •                 access_log.processed.2.gz          2024-10-8 01:24              10.5 KB rw- r-- r--            root               root      
    •                 access_log.processed.1.gz          2024-10-9 01:50              682 B    rw- r-- r--            root               root      
    •                 access_log.processed    2024-10-9 08:39              151 B    rw- r-- r--            root       root              
    •                 access_log



    Thank you in advance for your answer.  

    greeting, Jaap

     

    0
  • cPRex Jurassic Moderator

    Without that log file you'll be at the mercy of whatever support your host is willing to provide.

    0
  • Jaap van der linde

    I'm going to ask them and hope they give me the data.

    0
  • cPRex Jurassic Moderator

    Hopefully they are able to resolve the issue quickly!

    0
  • Jaap van der linde
    hey, I hope so too. I'm just looking and I see this:
    
    2024-10-09 16:14:55 2001:1c01:3802:5200:80da:89d5:7b68:b28e 404 GET /zorgeloosopmaat/ HTTP/1.0 https://uitvaartzorgvanderlinde.nl/ Mozilla/5.0 (Windows NT 10.0; Win64 ; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36 Edg/129.0.0.0 726
    
    in red, a page that he sometimes publishes and sometimes not. This also happens with other pages, including the home page.
    
    can you make anything out of this?
    
    greeting,
    Jaap
    0
  • cPRex Jurassic Moderator

    That is just a web request for a specific page and doesn't tell us anything about the specific problem behind the scenes, unfortunately.

    0
  • Jaap van der linde

    Hello,

    sorry, I hope to find something then. Unfortunately I don't know much about it. I need to purchase an additional product. What is best to do if that solves the problem. I like your sitebiler better than WP. This is just easier but with enough options.

     

    This is the response: 

     

    “Hello,

    As previously stated,
    As far as we are concerned, your 85923 uitvaartzorgvanderlinde.nl Confort service is working correctly.
    However, it seems that the problem is with the Sitejet Bulder application, so please contact the application's publisher so that they can help you.
    However, if the publisher tells you that the problem is with the host that is hosting your service, we suggest that you switch to a dedicated server service. (https://www.ikoula.nl/nl/dedicated-server)
    In this way, you will be able to act directly on the server itself.
    At the moment, you have a shared hosting service, which means that you share the resources of the server with other customers who have a service similar to yours.”

     

    Do you think this will solve it? the website really needs to be completely online as quickly as possible. I have something for that ;-). But I'd rather not throw money away.

    I hope you can advise me to do the right thing.

    Many thanks for your time.

     

    Greeting,

    Jaap

    0
  • cPRex Jurassic Moderator

    Since you are on a shared server your host likely has little support available for custom applications, so they may not be able to get the Sitejet tools working how you expect in that shared environment.  I'm not sure why that would be the case since they are built-in and completely supported by cPanel.

    Upgrading to a dedicated machine wouldn't change the issue, but the host is likely more willing to offer support for a much more expensive plan.

    I'm sorry I can't offer more details on my end, but with a shared account you are at the mercy of the host.

    0
  • Jaap van der linde

    #off topic | 


    Good morningcan you give me an advice, without any guarantee. Where I can find good hosting for my website. I will then have to transfer my domain name, no idea how long that will take. greeting,
    Jaap
    0
  • cPRex Jurassic Moderator

    I'm personally not able to recommend any specific hosting providers, but there is a lot of discussion about that topic over at https://www.webhostingtalk.com/

    0

Please sign in to leave a comment.