Works fine on local host, but not on Laravel Nova. The error is so generic as below.
Initially I thought its the timeout on Vapor, so I set it to 60 seconds, but the error still persists.
The document file failed to upload. No error logs whatsoever.
It's PHP problem
once you increase these values in php.ini you are good to go.
memory_limit
upload_max_filesize
post_max_size
you may need to restart apache
systemctl restart apache2
Related
Can anybody help me?
This error comes out
I have already tried entering the following code to the terminal and nothing.
rm -rf ~ / .bitnami / stackman
I have Big sur Version 11.3
error starting "XAMPP" stack
cannot calculate MAC address: Using fd 7 for I/O notifications
hv_vm_create HV_ERROR (unspecified error)
error starting "XAMPP" stack
For anyone still looking to resolve this error i solved my issue this way, this seemed to work for me and I tried all other methods using command line and older versions
Steps to reproduce:
download Xampp latest version
once downloaded and opened, navigate to manage servers.
click configure apache.
change the port to your port "8888"
open config file 'httpd.conf' and edit the port to your port eg.
#Listen 12.34.56.78:8888
Listen 8888
5b.
#ServerName www.example.com:##Port##
XAMPP
ServerName localhost:8888
repeat step 5 but for sql config file 'my.cnf' and for 'httpd-ssl.conf'giving them different ports
Restart the servers.
I'm using Docker for Windows and I am trying to install Shopware 6 with the dockware image.
When I enter command:
docker cp shopware:/var/www/html/. ./src
it copies some files, but after some waiting time I get the following error:
C:\mypath\src\vendor\shopware\administration\Resources\app\administration\node_modules\.cache\terser-webpack-plugin\content-v2\sha512\69\3c\9b1ea7d80f60c821b53797c0afe66e6b56c9637c96d7e70bbd16d7911ef6cd73eae0ac183fa8811f363a3c04742ad3efd1254748e650129d83c4b10522cb: The system cannot find the path specified
I also tried to install it on a different Windows-PC - same error.
Docker for Windows v 3.2.2
dockware/dev:6.3.5.1
I'm following these installation instructions: https://docs.dockware.io/development/start-developing
What I tried so far
using Windows cmd/Powershell/VSCode terminal
starting terminal(s) as administrator
using Docker for Windows v 2.5.0.0
using dockware/dev:6.3.2
Enable NTFS long paths (registry entry HKLM\SYSTEM\CurrentControlSet\Control\FileSystem)
It worked a few months ago, I don't know whats different this time...
Any ideas?
The error your are seeing is related to the webpack cache. Webpack is used to build the frontend code for shopware.
If the webpack processes are running, this cache can change often.
I would say this error is quite random and it's safe to ignore this error and try it again. What happens if you do you? Do you get an error on the same path or on a new one?
I have nextcloud installed and working fine in a docker but want to have fail2ban monitor the log files for brute force attempts. I know nextcloud has it's own baked in but it just throttles the log in attempts and I would like to all out ban them (I also have this problem with other containers as well). The docker-compose is set to create the nextcloud.log file to /mnt/nextcloud/log/nextcloud.log. I followed this guide to create the jail
https://www.c-rieger.de/nextcloud-installation-guide-ubuntu/#c06
Fail2ban is running on the host machine however, fail2ban fails to start with:
[447]: ERROR Failed during configuration: Have not found any log file for nextcloud jail
[447]: ERROR Async configuration of server failed
Thinking it was simply a permission issue, I chowned everything to root and tried to start again but still the service won't start. What am I doing wrong?
Thanks for the help!
The docker-compose is set to create the nextcloud.log file to /mnt/nextcloud/log/nextcloud.log
Be sure this file really exists and your jail.local has correct entry logpath:
[nextcloud]
...
logpath = /mnt/nextcloud/log/nextcloud.log
You can also check resulting config using dump:
fail2ban-client -d | grep 'nextcloud.*logpath'
But I'm still not sure the error message you provide was throwed by fail2ban, because its error messages look different, see https://github.com/fail2ban/fail2ban/commit/27947407bc7910f0f50972113218ebc73c4a22c7
It should be something like:
-have not found a log file for nextcloud log
+Have not found any log file for nextcloud jail
So I have finally gotten nginx + uWSGI running successfully for my Django install
however the problem I am having now is when I make changes to the code I need to restart the uWSGI process to view my changes
I feel like I am running the correct command here (i am very new to linux as well btw):
uwsgi --stop /var/run/uwsgi.pid
uwsgi --reload /var/run/uwsgi.pid
I get no error when I run these commands however my old code is still what loads
I also know its not a coding issue because I ran my django app in its development server and everything ran fine
The recommended way to signal reloading of application data is to use the --touch-reload option. Sample syntax on a .ini fine is:
touch-reload /var/run/uwsgi/app/myapp/reload
Where myappis your application name. /var/run/uwsgi/app is the recommended place for such files (could be anywhere). The reload file is an empty file whose timestamp is watched by uwsgi, whenever it changes (by, for example, using touch) uWSGI detects that change and restarts the corresponding uWSGI application instance.
So, whenever you update your code you should touch the file in order to update the in-memory version of the application. For example, on bash:
sudo touch /var/run/uwsgi/app/myapp/reload
Note --reload is an undocumented option on current uWSGI version.
I am trying to install symfony on wamp
http://trac.symfony-project.org/wiki/HowToInstallSymfonyOnWindowsWithWamp
when executed second step : pear install symfony/symfony
i got an error show below , how to go round
Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 7680 bytes) in /home/www/sf_projects/homepage/lib/vendor/symfony/lib/widget /sfWidgetFormDate.class.php on line 39
Just increase the memory limit for your PHP Environment by setting proper value inside php.ini
Looks like you're having just 16MB assigned, try inreasing this value.. common setting is for CLI environment.
memory_limit = 128M
You'll find the php.ini somewhere in your WAMP folder, after adjusting the value you need to restart the apache server.