+If your site uses a proxy to connect to the internet, you may use these settings to communicate with the outside world.
+The outside world still needs to be able to see your website, or this will not be very useful.
+
+#### Network Timeout
+
+How long to wait on a network communication before timing out.
+Value is in seconds.
+Default is 60 seconds.
+Set to 0 for unlimited (not recommended).
+
+#### Verify SSL Certificates
+
+By default Friendica allows SSL communication between websites that have "self-signed" SSL certificates.
+For the widest compatibility with browsers and other networks we do not recommend using self-signed certificates, but we will not prevent you from using them.
+SSL encrypts all the data transmitted between sites (and to your browser).
+This allows you to have completely encrypted communications, and also protect your login session from hijacking.
+Self-signed certificates can be generated for free, without paying top-dollar for a website SSL certificate.
+However these aren't looked upon favourably in the security community because they can be subject to so-called "man-in-the-middle" attacks.
+If you wish, you can turn on strict certificate checking.
+This will mean you cannot connect (at all) to self-signed SSL sites.
+
+#### Check upstream version
+
+If this option is enabled your Friendica node will check the upstream version once per day from the github repository.
+You can select if the stable version or the development version should be checked out.
+If there is a new version published, you will get notified in the admin panel summary page.
+
+### Auto Discovered Contact Directory
+
+### Performance
+
+### Worker
+
+This section allows you to configure the background process that is triggered by the `cron` job that was created during the installation.
+The process does check the available system resources before creating a new worker for a task.
+Because of this, it may happen that the maximum number of worker processes you allow will not be reached.
+
+If your server setup does not allow you to use the `proc_open` function of PHP, please disable it in this section.
+
+The tasks for the background process have priorities.
+To guarantee that important tasks are executed even though the system has a lot of work to do, it is useful to enable the *fastlane*.
+
+Should you not be able to run a cron job on your server, you can also activate the *frontend* worker.
+If you have done so, you can call `example.com/worker` (replace example.com with your actual domain name) on a regular basis from an external service.
+This will then trigger the execution of the background process.
+
+### Relocate
+
+## Users
+
+This section of the panel let the admin control the users registered on the node.
+
+If you have selected "Requires approval" for the *Register policy* in the general nodes configuration, new registrations will be listed at the top of the page.
+There the admin can then approve or disapprove the request.
+
+Below the new registration block the current accounts on the Friendica node are listed.
+You can sort the user list by name, email, registration date, date of last login, date of last posting and the account type.
+Here the admin can also block/unblock users from accessing the node or delete the accounts entirely.
+
+In the last section of the page admins can create new accounts on the node.
+The password for the new account will be send by email to the chosen email address.
+
+## Addons
+
+This page is for selecting and configuration of extensions for Friendica which have to be placed into the `/addon` subdirectory of your Friendica installation.
+You are presented with a long list of available addons.
+The name of each addon is linked to a separate page for that addon which offers more information and configuration possibilities.
+Also shown is the version of the addon and an indicator if the addon is currently active or not.
+
+When you update your node and the addons they may have to be reloaded.
+To simplify this process there is a button at the top of the page to reload all active Addons.
+
+## Themes
+
+The Themes section of the admin panel works similar to the Addons section but let you control the themes on your Friendica node.
+Each theme has a dedicated subpage showing the current status, some information about the theme and a screen-shot of the Friendica interface using the theme.
+Should the theme offer special settings, admins can set a global default value here.
+
+You can activate and deactivate themes on their dedicated sub-pages thus making them available for the users of the node.
+To select a default theme for the Friendica node, see the *Site* section of the admin panel.
+
+## Additional Features
+
+There are several optional features in Friendica like the *dislike* button.
+In this section of the admin panel you can select a default setting for your node and eventually fix it, so users cannot change the setting anymore.
+
+## DB Updates
+
+Should the database structure of Friendica change, it will apply the changes automatically.
+In case you are suspecting the update might not have worked, you can use this section of the admin panel to check the situation.
+
+## Inspect Queue
+
+In the admin panel summary there are two numbers for the message queues.
+The second number represents messages which could not be delivered and are queued for later retry.
+If this number goes sky-rocking you might ask yourself which recipient is not receiving.
+
+Behind the inspect queue section of the admin panel you will find a list of the messages that could not be delivered.
+The listing is sorted by the recipient name so identifying potential broken communication lines should be simple.
+These lines might be broken for various reasons.
+The receiving end might be off-line, there might be a high system load and so on.
+
+Don't panic!
+Friendica will not queue messages for all time but will sort out *dead* nodes automatically after a while and remove messages from the queue then.
+
+## Server Blocklist
+
+This page allows to block all communications (inbound and outbound) with a specific domain name.
+Each blocked domain entry requires a reason that will be displayed on the [friendica](/friendica) page.
+Matching is exact, blocking a domain doesn't block subdomains.
+
+## Federation Statistics
+
+The federation statistics page gives you a short summery of the nodes/servers/pods of the decentralized social network federation your node knows.
+These numbers are not complete and only contain nodes from networks Friendica federates directly with.
+
+## Delete Item
+
+Using this page an admin can delete postings and eventually associated discussion threads from their Friendica node.
+To do so, they need to know the GUID of the posting.
+This can be found on the `/display` page of the posting, it is the last part of the URL displayed in the browsers navigation bar.
+You can get to the `/display` page by following the *Link to source*.
+
+## Addon Features
+
+Some of the addons you can install for your Friendica node have settings which have to be set by the admin.
+All those addons will be listed in this area of the admin panels side bar with their names.
+
+## Logs
+
+The log section of the admin panel is separated into two pages.
+On the first, following the "log" link, you can configure how much Friendica shall log.
+And on the second you can read the log.
+
+You should not place your logs into any directory that is accessible from the web.
+If you have to, and you are using the default configuration from Apache, you should choose a name for the logfile ending in ``.log`` or ``.out``.
+Should you use another web server, please make sure that you have the correct access rules in place so that your log files are not accessible.
+
+There are five different log levels: Normal, Trace, Debug, Data and All.
+Specifying different verbosity of information and data written out to the log file.
+Normally you should not need to log at all.
+The *DEBUG* level will show a good deal of information about system activity but will not include detailed data.
+In the *ALL* level Friendica will log everything to the file.
+But due to the volume of information we recommend only enabling this when you are tracking down a specific problem.
+
+**The amount of data can grow the filesize of the logfile quickly**.
+You should set up some kind of [log rotation](https://en.wikipedia.org/wiki/Log_rotation) to keep the log file from growing too big.
+
+**Known Issues**: The filename ``friendica.log`` can cause problems depending on your server configuration (see [issue 2209](https://github.com/friendica/friendica/issues/2209)).
+
+By default PHP warnings and error messages are suppressed.
+If you want to enable those, you have to activate them in the ``config/local.config.php`` file.
+Use the following settings to redirect PHP errors to a file.