Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - EndMove

Pages: [1]
1
CentOS 7 Problems / Re: Cron spot does not work
« on: September 05, 2019, 07:11:49 PM »
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
● crond.service - Command Scheduler
   Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2019-09-05 21:09:46 CEST; 35s ago
  Process: 9154 ExecStart=/usr/sbin/crond -n $CRONDARGS (code=exited, status=1/FAILURE)
 Main PID: 9154 (code=exited, status=1/FAILURE)

Sep 05 21:09:46 panel.softalabs.com systemd[1]: Started Command Scheduler.
Sep 05 21:09:46 panel.softalabs.com crond[9154]: crond: can't lock /var/run/crond.pid, otherpid may be 3448: Resource temporarily unavailable
Sep 05 21:09:46 panel.softalabs.com systemd[1]: crond.service: main process exited, code=exited, status=1/FAILURE
Sep 05 21:09:46 panel.softalabs.com systemd[1]: Unit crond.service entered failed state.
Sep 05 21:09:46 panel.softalabs.com systemd[1]: crond.service failed.
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

2
CentOS 7 Problems / Cron spot does not work
« on: September 05, 2019, 06:49:07 PM »
Hello, cron spot does not work on my panel I really need can you help me? or explain to me how to re install all cron spot system?


https://www.noelshack.com/2019-36-4-1567709339-capture.png

3
Apache / Re: Server unable to read htaccess file, denying access to be safe
« on: September 04, 2019, 05:50:52 PM »
UP

4
Apache / Re: Server unable to read htaccess file, denying access to be safe
« on: September 01, 2019, 02:15:05 PM »
Hi Evansa,
Yes when I create a subdomain, the permissions are not good.

5
Apache / Server unable to read htaccess file, denying access to be safe
« on: August 31, 2019, 02:05:53 PM »
Hello,
I recently installed your panel. I found an annoying problem ... When a user chalks a subdomain a 403 error occurs.

I found a solution, but this solution must be done manually. : /
I would like a solution on the long term and automatic. (correct the problem) how can I do?

Here is an image of the problem and an image of the manual solution:

https://www.noelshack.com/2019-35-6-1567260317-capture1.png

https://www.noelshack.com/2019-35-6-1567260317-capture2.png

Pages: [1]