"Bad server response"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • luc
    Junior Member
    • Apr 2021
    • 18

    "Bad server response"


    I need your urgent help, please I tried to rename a field from admin> entities> edit, and now I get

    "Bad server response"


    And now it won't let me enter the server

    Someone who can help me solve this problem please, I really urge
    Last edited by luc; 04-12-2021, 08:52 PM.
  • item
    Active Community Member
    • Mar 2017
    • 1489

    #2
    Hello,

    you need ssh and run these command : rebuild, clear_cache


    what say log file ?
    If you could give the project a star on GitHub. EspoCrm believe our work truly deserves more recognition. Thanks.​

    Comment


    • luc
      luc commented
      Editing a comment
      ssh is to back up my information?
  • item
    Active Community Member
    • Mar 2017
    • 1489

    #3
    No,
    it's for have result (log) of command rebuild , clear_cache !
    If you could give the project a star on GitHub. EspoCrm believe our work truly deserves more recognition. Thanks.​

    Comment

    • victor
      Active Community Member
      • Aug 2022
      • 755

      #4
      I updated php from 8.1 to 8.2 and also got Bad server response error.
      It is worth saying that I received it only on one instance that was active in Chrome (the main, not anonymous tab) at the time of the php update.
      Everything in this instance worked as it should, but I was annoyed by the red pop-up inscription Bad server response​.
      All other instances also worked properly on the new php 8.2 and there was no such error.
      - I made rebuild and cleared the cache as suggested above in UI (In Administration > Rebuild and Administration > Clear Cashe).
      - Did the same via CLI.
      - Restarted the virtual machine.
      - Restarted apache.
      - I checked the server logs and EspoCRM logs - no hint of an error.​

      Solution: I just went to this instance from an anonymous tab (it was possible in another browser) and the problem disappeared. That is, in my case, it was a story with an uncleaned browser cache.

      Comment

      Working...