Tag Info

Hot answers tagged

5

It looks like the problem is caused because when you added your open all line you used iptables -A INPUT ... which has dutifully added it to the end of the INPUT chain right after the REJECT all rule. As iptables works on first match wins your accept all rule is never matched so port 3000 is blocked. You should use iptables -I... to insert rules into a ...


5

Looks like everything under /wp-content/ is throwing a 301 redirect. Look there for what is likely a malicious .htaccess file - may be a breached account or a vulnerability in WordPress allowing upload (make sure your WP is fully up to date). Beyond that - depending on the attack vector, there may be more aspects of the system compromised; the conventional ...


4

You just have to register AdminUser as a manageable resource: $> rails generate active_admin:resource AdminUser Then, just customize the whole thing but remember that both 'password' and 'password_confirmation' field have to be present in the form if you want to be able to manipulate passwords - you decide if that's a good idea. I did it like this but ...


4

It sounds like your application needs better design and lacks appropriate parallelism unless you're actually rendering those pages in some way, and even then I think you should be able to surpass 8 per second if you uncouple the downloading from the final render -- interactivity is not a priority. You are best served by ensuring proper parallelism in your ...


4

Security through obscurity is not security. That being said, if you are seeing a lot of malicious attempts, I would examine all logs from the source IP's of the problem children regularly and carefully, looking for cases of successful actions... success from those sorts of places would be bad.


3

I'm trying to segment a few servers for a Rails project and part of that is entertaining the idea of isolating Resque workers to their own box. I already have Redis broken out, but is it common to put Resque workers elsewhere? I'm going to make this a bit more generic. Is it common to put job processing workers on different machines than the ...


3

It's unusual to go co-lo with only one server and only one sysadmin. The point at which it seems worthwhile to me is at about 20 servers and two sysadmins. Some of the benefits that having your servers managed can provide you are: 24/7 monitoring Remote hands In-stock spare parts Backups With only one server, your backups are tied to the same hardware ...


2

Fedora 16 has migrated to systemd from traditional init.d layout, so you should run su - postgres -c "PGDATA=/var/lib/pgsql/data initdb" directly, see Fedora wiki


2

Yes, you can use Apache and Passenger to run multiple Rails applications. If you only have one instance, then you don't need a load balancer, and name-based virtual hosting is orthogonal to the use of a load balancer. You can run Rails applications that require different versions on the one machine; there's probably no documentation because it's so ...


2

All you need is a second server { block that's configured for SSL on port 443. You'll want a listen 443 ssl; directive and directives pointing to your public and private keys; ssl_certificate /path/to/webserver-cert.pem; and ssl_certificate_key /path/to/webserver-key.pem;.


2

Based on the documentation, you will need to disable MultiViews on the passenger sites. Additionally, your DocumentRoot should point to the directory containing public--i.e., Passenger checks to see if the selected directory contains a passenger application by checking for {DocumentRoot}/../config/environment.rb, so verify that this is correct. If you're ...


2

There isn't a recommended tutorial. Since the system-provided ruby for Squeeze is a Ruby1.8, your Ruby 1.9 install will not be able to use system-ruby. You'll have to install 1.9 some other way, probably via rvm. At this point you're out of the land of "RoR on DebSqueeze" and into the land of "RoR on Apache on Linux", which is a much better documented ...


2

The "hacking attempts" you see in your logs are probably nothing to be concerned about. If everything looks like it was run by some kind of automated script, following good security practices (such as those found in the Rails Guide) is probably adequate. However, if you see evidence that someone is targeting you specifically, I'd take it more seriously. ...


2

To prevent clients from forging a proxy's headers, both X-Forwarded-For and Client-Ip have to equal to not raise this kind of error. Simply set the Client-Ip header in your nginx config: As for the IP addresses in your log: 192.168.255.5 probably is NodeBalancer's internal IP (examples in Linode Library show 192.168.0.0/16 subnet as usual; that should ...


2

Aws can provide the scalability in case you need it Architecture suggestions use elb for first tier use two or more app servers (for redundancy reasons) use rds if you can Now ... If rds is not an option you will end up with a master db and a slave. For the db I recommend ebs volumes that are striped. Config management it can be anything really as ...


1

Managed to solve this guys. Further investigation showed larges amounts of network traffic (and cpu usage!) between the times of 12am - 4am. It turns out, our bing webmaster settings were set to "high" between these times, causing bingbot to go crazy and absolutely hammer unicorn. (poor unicorn). More info; ...


1

you can install phusion-passenger and use Apache2 as web server using mod-proxy, ProxyPass and ProxyPassReverse, it's very easy the setup in a VirtualHost only type this lines into VirtualHost: ProxyPass / http://0.0.0.0:port/ ProxyPassReverse / http://0.0.0.0:port/ With this you will have configured your Apache server also enables the mods for proxy ...


1

I've found that excessive stats to /etc/localtime are due to missing environment variables. Try this: echo $TZ If it's blank, then set the variable in the correct location (i.e. /home/apache/.bash_profile). You'll need to set it for the user responsible for running your webserver, then reload the daemon (apachectl graceful etc). TZ='Europe/London'; ...


1

I did this plugin, check it out! https://github.com/jbox-web/redmine-gitolite This works with Redmine 2.x only I've finally updated Redmine Git Hosting from Kubitron's You can check out it here https://github.com/jbox-web/redmine_git_hosting This one is compatible with Redmine 1.x and 2.x. The differences are : a cleaner indentation, the code is a ...


1

It seems there are currently a lot of people working on "2.0-migration" branches of the redmine_git_hosting plugin originally made by Eric Paul Bishop on GitHub. Currently the most advanced of the forks containing these branches is the one by a guy called zucchi. After looking around for some time, I guess there is no production-ready variant of the plugin ...


1

Check here. Below the file list, there's an online readme with a general configuration strategy and a long step-by-step configuration section that might be helpful.


1

It's quite easy, since Passenger 3.2 will support different ruby versions out-of-the box. Only thing is, 3.2 has not been released yet. Just make sure you set the proper passenger_ruby and RVM/Capistrano can do the rest. Read more in this article: http://ariejan.net/2012/05/11/running-a-different-ruby-with-passenger-3-2-and-rvm Note that I do run 3.2 on ...


1

Rack processes are the application servers running your site code not Passenger. I'd suspect problems with the recent upgrades and all the usual troubleshooting around that. Here's what a request looks like on your system. user -> nginx -> passenger -> Rack process -> generates page You system will have multiple Rack processes because each is ...


1

"System user" is a very ambiguous statement. Regardless, a general rule of thumb is to give each service its own specific user, and that user should only have permissions to its own application space (i.e., your apache user shouldn't be able to mess with what your bind user controls, and vice versa). Moreover, those users shouldn't have any "system" ...


1

Reading the link you provide it says For PostgreSQL version 9.0 and above, the <name> is postgresql-9.0... and later is says service <name> initdb so I'm guessing you want service postgresql-9.0 initdb


1

10.X.X.X is a local network address, so without being inside your building, we can't tell what it is from here Look in the nginx access logs -- is nginx logging multiple requests happening? If so, looking at the user-agent string should tell you what software is making them


1

I'd start by tracing the request-path through the entire stack. It could look something like this: The request is received at TCP/80 on Websrv. Nginx is bound to TCP/80 and processes the request The request is handled by these specific directives in the config file The request is passed off to Passenger, where it enters the Ruby environment If I had to ...


1

Check your config/database.yml, the development and production environment might have different DB settings. Remember to create the database in production env(RailsEnv), or just copy the credentials under development section to production section in config/database.yml Installing PG & Apache as root is nothing wrong, that's the right way to protect ...



Only top voted, non community-wiki answers of a minimum length are eligible