I have two openx 2.8 servers running here. The issue is that trying to open the admin page redirects me to the full path www.myserver.com/www/admin/index.php with blank screen. Still I can access www.myserver.com/www/images/, delivery etc. I tried a lot of stuff without any success.
this one doesn't work for me OpenX Admin not accessible
I had something similar happen to me last week. Check your configuration file in the /var folder of your openx installation, probably called something like www.yoursite.com.conf.php. Mine was corrupted. I suspect outside malicious activity, especially since there are known vulnerabilities in OpenX.. I'm currently looking at upgrading to Revive Ad server, which is the successor and is supposed to offer a complete upgrade path.
Related
Currently I am trying to run a Wordpress repo locally for development. I am not using MAMP pro even though I still have a 9 day trail. I figured since I'm going to be using the free version for now I might as well work with that. I have my Apache & MySQL server running along with the Document Root pointing to my Sites folder where my projectName repo sits. I'm still running off of the default port of Apache 8888.
After I start the servers, I open WebStart and import my DB into phpMyAdmin. Everything works perfectly fine and the copy of my db gets imported. I then make sure that my wp-config.php file has the appropriate settings to access this db. I then click on My Website. This pulls up the content of the website. However, it does not pull in any of the assets(imgs/js/css). I receive the following errors in the console:
Failed to load resource: net::ERR_EMPTY_RESPONSE http://projectName.dev/wp-content/uploads/2016/09/logo-footer-1.png
Failed to load resource: net::ERR_EMPTY_RESPONSE http://projectName.dev/wp-content/themes/projectName/images/circle.png
And so the list goes on and on for pretty much every asset the project could possibly have. Now configuration is NOT my strong suit, and at this point I am at a loss of what could possibly be happening. Awhile ago I did follow a tutorial on how to setup my files so that I can access them in the web browser by simply typing the name of the project with the domain .dev, example: projectName.dev. I started having issues with this after upgrading to OS Sierra and it no longer works. Could this possibly be the reason as to why it is looking for these assets in the projectName at the .dev domain?
I apologize if this does not make sense. I am willing to provide anyone with any information on this as I need as much help as possible because I still need to level up my configuration skills. Let me know if you have questions.
The images and other assets are referenced with an absolute filepath (i.e. the URL of the server on which you first set it up). This has to be changed in all database entries. There are tutorials for this on the net, but the most simple version is to open the sql file in an editor and search & replace the general URL part in the complete database.
Be sure to keep a backup of the file - that might not work on the first try...
Just today when I tried to access my site I got a warning saying my site has harmful content.
I have tried scanning the site with clamAV and some other online sites for virus scan but did not find anything. I submitted my site to Google and it is still saying it is malicious. There is no sample URL for the malware, it only says "Undetermined malware"
I am using WordPress, there was no plugin updated recently. How can I find which part of my site is infected?
I tried console of google chrome, tried installing new anti-malware plugin (nothing found), tried to scan the site with different other websites and such but nothing gave any positive result.
Security on a website is very different from security on a home computer. Fixing this will be hard for someone who knows what they are doing, you have a lot of learning to do ahead of you before you will be able to accomplish this effectively. As a first step you need to try to identify when the problem started and revert to an earlier backup. Then remove ALL plugins, upgrade your WordPress installation to the latest version then change all the passwords associated with your site, then ONLY install the absolutely essential plugins - and make sure its the latest production versions of these.
This might fix the problem.
I have previously installed several different Joomla installation at the same hosting company without any major faults that couldn't be corrected quickly. Though I must say that I now find myself lost and don't know where to turn.. So here I am.
I have mulitple issues that I believe is all connected somehow.
Can't upload Images using the Media Uploader (Image size too large) though everything is set up correctly (max_file_size etc.) in PHP configurations and Joomla config.
Can't upload any other files in the Extension Manager either, since it says my PHP temp folder is not set. Though it is set, and writeble, have permissions etc. Also more than triplechecked the path, by FTP upload PHP-files to write out and verify the absolute path.
When I save something in the Global Configuration, it says my "Configuration.php" file is not writable. Permission is set to 777 even! If I go back and check, my settings is saved though it just said it couldn't save to the file?
Even tried to change to FTP-upload to see if I could bypass the fault somehow, tried both by setting it in Global Settings and by downloading the config file, change it manually and then re-upload it via FTP. No luck there either, seemed to just ignore my settings..
Updating Joomla seems to go just fine though, just updated to 3.4.1 to see if it made any difference but no. Running on PHP 5.6 right now though my hostingcompany just said they will downgrade to 5.4 to see if can make something change.
Otherwise, the website is fully functional! You can browse as usual, and write blogs etc. Though, not upload anything. Saving other settings work fine though. Should also mention that the website worked locally 100% before uploaded to the current server.
Any ideas where to start looking? Been Googling for the last 8 hours!
My webhost downgraded my PHP service to 5.4 instead, which solved all problems. Weird.
I have a simple Joomla site, sometimes it dies. I found a file containing the following code:
if(date('s',time())%2==0) die();
I deleted the code, and then it appeared in another file.
When I download the site via Akeeba and install it on localhost, and then delete all the bad code then the site is clean (and the virus doesn't return). But in my server the virus is still active.
Any idea how to fix the problem?
Please help me!
You probably have a vulnerability in the website that a script or hacker is exploiting to reinfect the website.
Make sure you have updated to the latest version of Joomla in the series. For example this is currently Joomla 3.3.6 for the Joomla 3.x series.
More likely the issue is with a third party extension. Make a list of third party extensions via Extension Manager (the third party extensions are the ones that have something other than "Joomla Project" as the author). Remember that not all extensions use the Joomla updater so some updates have to be done manually. Run through the list and check that you are using all the latest versions. You can find the latest versions via http://extensions.joomla.org and/or the developer websites.
You should also check http://vel.joomla.org/ to ensure that you are not using any vulnerable extensions.
You should also reset administrator password(s), the database password and your hosting password.
Repeat the above steps for any other websites that share the same web hosting account.
Check that any CRON jobs in your hosting account are legitimate.
If you are serious about eradicating malware from your website, you should probably subscribe to myJoomla.com or have the website professionally scanned by Sucuri or some other security expert.
Alternatively, you may be able to eradicate the malware by deleting the website and restoring from a backup or deleting the website and rebuilding it from scratch taking care not to reintroduce the malware from backed up files.
I have just moved a silverstripe install to a new joyent smartos server. Not being familiar with Linux, this was still relatively easy.
I am new to silverstripe as well, but the team here has developed on it for years.
I have the site up and running on the new server, but have not pointed the domain to it until we can thoroughly test it. So I am accessing it from it's ip address. The site displays fine and the sub pages work as well. When I navigate to the '/admin' page, I see a silverstripe page that states the page cannot be found (not an Apache 404). I copied over the .htaccess and the _config.php from the old server, so there should be no issues.
I have done a /dev/build with no errors and I can log in through the security page, but I just cannot get the /admin to come up. I am lost after spending the whole morning surfing google to find the answer. Any help would be greatly appreciated.
UPDATE:: I installed a fresh version of silverstripe into a subdirectory on the same server. Works perfectly, so that rules out any PHP issues.
I have also tried /index.php/admin with no luck.
Thanks,
Ben
I was having this problem as well. None of the solutions I found online worked for me, but I managed to figure it out.
I had apache running as a non-standard user, and the problem turned out to be that the webserver was unable to save session data for the logins.
The solution in my case was to chown root.myuser /var/lib/php/session. Once done, the admin page loaded fine.
If /admin is not loading at all and there is no 404 error, there is a high chance of a PHP error. And that should be logged in the webserver's log file. This will depend on your operating system and probably on the Joyent environment (not familiar with that breed of cloud computing). On Debian, Ubuntu, and some more it's /var/log/apache2/error.log (assuming you're using Apache).
If I had to guess, I'd say the permissions of assets/_combinedfiles/ are bad. The webserver tries to create some combined JS and CSS files there (specifically leftandmain.js and cmsmain.js) and if it fails, you might get the dreaded white page of death in /admin.