Jekyll doesn’t server after updating my Mac to El Capitan and Jekyll itself any more. While it appears that it actually is generating the site, there is no indication that it would listen to some port in the console.
There’s no other thing running on the same port.
Here’s what I did:
Upgraded to El Capitan
After receiving “unknown command” when I typed in “jekyll” into the console I did
sudo gem install -n /usr/local/bin GEM_NAME_HERE
like suggested here (https://github.com/sass/sass/issues/1768)
Updated Jekyll
I’m unfortunately not able to tell if it was actually the OS update or the Jekyll update that caused this.
Does anyone have a hint?
My Jekyll-Version is 2.5.3.
Related
I am trying to run the following command but I am getting the error like
pa11y http://example.com/ # Trying to run this on my terminal
Welcome to Pa11y
------------------------
Error: Chromium revision is not downloaded. Run "npm install" or "yarn install"
at Launcher.launch (/usr/lib/node_modules/pa11y/node_modules/puppeteer/lib/Launcher.js:119:15)
at async runPa11yTest (/usr/lib/node_modules/pa11y/lib/pa11y.js:106:29)
at async pa11y (/usr/lib/node_modules/pa11y/lib/pa11y.js:55:19)
at async runProgram (/usr/lib/node_modules/pa11y/bin/pa11y.js:122:19)
I spent around 3-4 hours to fix this but no luck. I have tried every possible solution on the internet which is posted by others who had faced similar errors.
Any help in this regard is helpful
Two questions:
Do you have Chromium installed? pa11y doesn't think so! It could be a wrong version installed if so, or installed in a way that pa11y can't find.
What OS are you running?
The answer to your question depends on your Operating System, because the version of Chromium you need is specific to your OS! If you're running Linux Alpine,
the command would be something like this:
apk add -U --no-cache --allow-untrusted udev ttf-freefont chromium git
I had this problem when trying to run the Node package puppeteer (which uses Chromium) in a Docker container running node 12 alpine. I spent all weekend (yes...) to come to the 1 line (yes...) I needed. It turned out I needed to add the above line to my Dockerfile, which installs the necessary fonts and libraries and installs Chromium.
I also had to tell Puppeteer to skip installing Chromium, but I don't think that's applicable to your situation.
If you're running something other than Linux, check out these instructions for installing Chromium: https://www.chromium.org/getting-involved/download-chromium
I'm having a strange issue with Ubuntu 18.04 and Nginx with ModSecurity. I've compiled everything correctly and it's working when activating the ModSecurity module, however whenever I activate a rule, I get the following:
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_M_construct null not valid
Nginx crashes and doesn't serve the page - any ideas?
I'm having this issue in Ubuntu 16.04 as well. This seems to be an issue with the latest version of ModSecurity as seen in this bug: https://github.com/SpiderLabs/ModSecurity/issues/2180
If you downloaded ModSecurity via git, you can use this command to get back to a working version:
git reset --hard d5b93c1013ca9c9a96c75369576b54832e9a2b48
Then clean your ModSecurity build directory and build it again. Once you have ModSecurity rebuild, restart nginx. Once the above bug is closed in GitHub, it will probably be safe to update to the latest version again.
Edit: This issue has been corrected. Simply update and recompile ModSecurity.
Please I need help on this project, I have wamp server to run the project on symphony.Look at the error display on my web browser ,when load the project from wamp server
If I run this code from my command prompt see the results php app/check.php
If I run this code from my command prompt see the results php app/check.php
php app/console server:run
It looks like you also have XAMPP installed on your system, or did at one time.
See the line that says
Configuration file used in PHP : C:\xampp\php\php.ini
^^^^^
I would suggest that you check your Windows PATH. I guess XAMPP might have added it's own PHP version into the PATH.
Alternatively you could uninstall XAMPP, but make sure you back everything up, code/databases etc before you uninstall it.
WAMPServer does not need anything placed on the Windows PATH, and if you do it makes switching versions of PHP far more complicated and prone to mistakes.
Have a look at this answer for how to make the PHP CLI as flexible as WAMPServer when it comes to running PHP code on different versions of PHP from the command line.
It also looks like you have not istalled composer. Follow the instructions on how to instal composed from the error messages. Or have a look at the composer site for help
I am trying to compile ModSecurity for the Nginx OSS web server. I have followed all of the instructions from their "Quick Start Guide", but am running into an issue. After linking up the new module, the config test fails.
Error output from /var/log/nginx/error.log is:
2018/02/10 00:47:51 [emerg] 6026#6026: module "/usr/share/nginx/modules/ngx_http_modsecurity_module.so" is not binary compatible in /etc/nginx/modules-enabled/50-mod-http-modsecurity.conf:1
originally the dynamic module was compiled with
sh
./configure --with-compat --add-dynamic-module=../ModSecurity-nginx
but this results in the error.
from what I've read, I need to compile the module with identical options as the existing Nginx instance.
I found the current options using nginx -V, and then re-ran the ./configure using all of the output options, but this gives the same error.
Can anyone point me down the right path here?
Thanks for any help.
UPDATE 10/29/18
It seems the original binary also needs to be compiled with the --with-compat flag. I have submitted a bug report on the issue that can be found here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897926
Maybe it can get some traction.
I had a similar issue. I was using Nginx 1.10.3 which is the default for Debian Stretch. This version does not seem to work with the latest Nginx ModSecurity connector.
I removed the default Nginx version and installed the latest stable Nginx from http://nginx.org/en/linux_packages.html. After that I was able to install and load the ModSecurity module for Nginx without problems. I followed this guide: https://www.linuxjournal.com/content/modsecurity-and-nginx for installing the ModSecurity module for Nginx.
The latest stable version of Nginx which is 1.14.2 supports the --with-compat flag. When compiling Nginx source code make sure to use the same compiler options that were used with your running Nginx. To find out which compile time options were used to build your currently running Nginx, run the command: nginx -V
I've followed the instructions for installing phusion passenger with nginx in ubuntu. I had some issues while installing since I use rvm and I had to install as root and the installer was failing to find rake so i temporarily chmoded /opt to be owned by my user and after installation I resetted ownership to root. I can see nginx welcome page but when I try to visit a sinatra app I get forbidden, the virtual host is pointed to the sinatra app public dir and the permissions for the whole app are 777.
Try Passenger 3. It automatically detects most permission problems and tells you how to fix them.
If this is for a production system, you really don't need the flexibility of RVM as you should be using a single stable version of Ruby and Rails for Phusion. Install the version you need, using Aptitude if that version is available, and be done with it.
Because this is the page that Google brought me to for my issue, which isn't a Passenger issue, but a Nginx reverse-proxy issue, you need to add the line
disable :protection
somewhere in your sinatra app. I have mine at the very end, outside any method (in global scope).
Well my mistake was not using rvmsudo to install nginx with passenger, instructions here: http://rvm.io/integration/passenger/.