similar to: redirect

On the server [root@bangvmpllDA02 logs]# ruby -v ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] [root@bangvmpllDA02 logs]# puppet --version 3.0.1 and [root@bangvmpllDA02 logs]# service nginx configtest nginx: the configuration file /apps/nginx/nginx.conf syntax is ok nginx: configuration file /apps/nginx/nginx.conf test is successful [root@bangvmpllDA02 logs]# service nginx status

Hi All, I am setting up puppetmaster with nginx and passenger and separating the Puppetmaster primary CA server. I have 3 host loadbalancer01 - Nginx doing LB on IP address and also running puppetmaster with passenger under 127.0.0.1 (port 8140). primaryca - Puppetmaster Primary CA pclient - Puppet Client The did the following steps: On Primary CA server: ---------------------------- cd

Hi, It seems that webrick cannot handle too much client and that luke is making mongrel the ''default'' server to use so i wanted to switch to mongrel. Then i read that i cannot use directly mongrel like webrick because it does not speak SSL. So my issue is : how to be sure things stay secure in the way that the proxy should be the one speaking ssl and making client ssl

Hey, Just wondering if anyone else has noticed this. I''m using thin+puppetmasterd+nginx. If i add a host, sign it''s key, run puppetd successfully on it all is good, as expected. If i then revoke/clean the key on the master server, leave the box running, startup another host set the hostname to be the same as the old, generate new keys/have them signed. The original box is still

Hi, I''ve created two Nginx patches (see at the end of this message) to allow a simpler Nginx configuration for your Mongrel puppetmasters. The two main issues with Nginx in front of puppet were: * no CRL support * no optional certificate verification (and thus we''re forced to have two separate configs on two different ports, and to use --ca_port). Now, it is as simple as

Hello all, I''d like to have nginx+passenger show the custom (Default) error pages when a HTTP 500 error occurs in my app. I am running a rails 2.3 app on nginx 1.2 with passenger 3.0.7 Here is my nginx config file: #user nobody; worker_processes 16; error_log /opt/nginx/logs/error.log info; pid /opt/nginx/logs/nginx.pid; worker_rlimit_nofile 32768; events {

Dear friends, I followed the guide on http://techoctave.com/c7/posts/16-how-to-host-a-rails-app-with-phusion-passenger-for-nginx and successfully deployed two apps on the same web server, some months ago. Then when I upgraded to Rails 2.3.13.rc1 everything seems to be OK, but when I visit my app with the browser all that I get is the Welcome page from Nginx. Here is my nginx.conf:

Hi, Is there a way to upload files to nginx webserver https://software.mydomain.com from the browser ? I have the below nginx config file. I am running nginx version: nginx/1.24.0 on CentOS Linux release 7.9.2009 (Core) # nginx -v nginx version: nginx/1.24.0 # cat /etc/redhat-release CentOS Linux release 7.9.2009 (Core) # *cat /etc/nginx/conf.d/default.conf* > server { > listen

I am struggling to get icecast running with https, but I cannot get it working My environment is: Debian 10 (Buster) I tried the standard debian package but there is no SSL capability at all. So I compiled the icecast-2.4.4.tar.gz contents with ./configure --with-curl --with-openssl; make; make install I always get the error: [2020-02-05 17:35:36] INFO connection/get_ssl_certificate

Hi, Im using nginx and rails for my site which contains url with georgian letters ie განცხადებები so something like http://gancxadebebi.ge/ka/%E1%83%92%E1%83%90%E1%83%9C%E1%83%AA%E1%83%AE%E1%83%90%E1%83%93%E1%83%94%E1%83%91%E1%83%94%E1%83%91%E1%83%98 It is mainly working perfectly but sometimes I receive request with truncated url ie 1 -

I upgraded Puppet master from 2.7.6 to 2.7.20 on CentOS5.8_x86_64. But when I tried to launch ''puppet agent -t'' on one of staging servers, the puppet daemon did not work and got heaps errors. I have no idea what made it wrong and how to fix it. Retrieving plugin [0m Failed to generate additional resources using ''eval_generate: Error 500 on SERVER: <!DOCTYPE HTML

Q1) I can't get ssl_verify_client_cert=yes working. The ssl key and cert are signed using our CA. Also the ssl_ca_file has a CRL appended (no revokes yet). Expected behavior: Stop the SSL (the client doesn't have a cert installed) Current behavior: Mail clients accepts SSL and login succeeds. (both Evolution and Thunderbird). My bad? Please advise. Q2) The next step, if dovecot blocks

In Rails 2.3.x, you can override render_optional_error_file like so: # ApplicationController.rb protected def render_optional_error_file(status_code) render :template => "errors/500", :status => 500, :layout => ''application'' end However, Rails 3 no longer has render_optional_error_file. Instead, you need to overriderescue_action_in_public, which I do:

éÚÍÅÎÅÎÉÑ × nginx 0.8.47 28.07.2010 *) éÓÐÒÁ×ÌÅÎÉÅ: ÐÅÒÅÍÅÎÎÁÑ $request_time ÉÍÅÌÁ ÎÅ×ÅÒÎÙÅ ÚÎÁÞÅÎÉÑ ÄÌÑ ÐÏÄÚÁÐÒÏÓÏ×. *) éÓÐÒÁ×ÌÅÎÉÅ: ÏÛÉÂËÉ, ÐÅÒÅÈ×ÁÞÅÎÎÙÅ error_page, ÎÅ ËÜÛÉÒÏ×ÁÌÉÓØ. *) éÓÐÒÁ×ÌÅÎÉÅ: ÅÓÌÉ ÉÓÐÏÌØÚÏ×ÁÌÓÑ ÐÁÒÁÍÅÔÒ max_size, ÔÏ cache manager ÍÏÇ ÚÁÃÉËÌÉÔØÓÑ. ÏÛÉÂËÁ ÐÏÑ×ÉÌÁÓØ × 0.8.46. -- éÇÏÒØ óÙÓÏÅ×

Изменения в nginx 1.23.4 28.03.2023 *) Изменение: теперь протокол TLSv1.3 разрешён по умолчанию. *) Изменение: теперь nginx выдаёт предупреждение при переопределении параметров listen-сокета, задающих используемые протоколы. *) Изменение: теперь, если клиент использует pipelining, nginx закрывает соединения с ожиданием

Does someone know how to tell mongrel_rails to read the public/system/maintenance.html file? -- Posted via http://www.ruby-forum.com/.

I am using mongrel_cluster with mod_proxy_balancer and would like to enable compression (assuming it improves throughtput) and limit file size upload. I configured mod_deflate and LimitRequestSize in Apache, but in my trials looks like the proxied calls bypass those directives (the conf goes below). Is there a way to get this? -- fxn # Adapt this .example locally, as usual. # # To be

If you append an extra percent sign to a URL that gets passed to mongrel, it will return a Bad Request error. Kind of odd that "http://localhost/%" causes a "Bad Request" instead of a "Not Found" error. Here is the error from the mongrel log: HTTP parse error, malformed request (127.0.0.1): #<Mongrel::HttpParserError: Invalid HTTP format, parsing fails.>

On 04/09/2015 12:46 PM, Alfred von Campe wrote: > What I am really looking for is where gdm (or whatever) caches > the list of users who have previously logged in to a system. I > have tried the brute force approach (grep -R) without success. It's a dbus service. # rpm -qf /etc/dbus-1/system.d/org.freedesktop.Accounts.conf accountsservice-0.6.39-2.fc21.x86_64 Documentation in:

Over the years many shops have come to start running puppet via cron to address memory leaks in earlier versions of Ruby, but the official position was that puppet was meant to be run as a continually running service. I am wondering if the official position has changed. On one hand many if not all of the early Ruby issues have been fixed, on the other, the addition of mcollective into the mix as