WordPress Umzug Internal Server Error


  • General (6)
  • Third-Party Software (8)
  • 3CX (3)
  • ISPConfig (1)
  • Snom (1)
  • SpamExperts (2)
  • Linux (7)
    • CentOS (2)
    • Cisco (1)
    • Hersteller (1)
      • IBM / Lenovo (1)
      • Hosting How-Tos (1)
      • Scripts (2)
      • VMWare (1)
      • Windows (55)
        • Clients (9)
          • Office (5)
          • SecureDrive (1)
          • Server (49)
            • Certificates (2)
            • ADFS (3)
            • CRM (7)
            • Exchange (17)
            • Freeswitch (1)
            • Hyper-V (6)
            • IIS (1)
            • Lync (3)
            • SharePoint (5)
            • SQL (1)
            • Terminal/RD Services (2)
            • VMM (1)
            • WSUS (1)
            • Zabbix (2)
            • Category: Freeswitch

              Freeswitch – Endlich vernünftig debuggen

              Um Freeswitch ordentlich debuggen zu können, sind folgende Konsolenbefehle hilfreich:

              Loglevel der Konsole setzen:
              console loglevel – Gibt das aktuelle Loglevel aus
              console loglevel [0-7] – Stellt das Loglevel ein

              Beschreibung der Loglevel:
              0 – Console (Hotkey F7)
              1 – Alert
              2 – Critical
              3 – Error
              4 – Warning
              5 – Notice
              6 – Info
              7 – Debug (Hotkey F8)

              SIP-Logging aktivieren:
              sofia profile internal siptrace on – Aktiviert SIP-Logs für interne Kommunikation
              sofia profile external siptrace on – Aktiviert SIP-Logs für externe Kommunikation

              Einfärben der Konsole:
              console colorize [on|off|toggle] – Aktiviert/Deaktiviert die Einfärbung

              Secure your site with HTTPS

              What is HTTPS?

              HTTPS (Hypertext Transfer Protocol Secure) is an internet communication protocol that protects the integrity and confidentiality of data between the user’s computer and the site. Users expect a secure and private online experience when using a website. We encourage you to adopt HTTPS in order to protect your users’ connections to your website, regardless of the content on the site.

              Data sent using HTTPS is secured via Transport Layer Security protocol (TLS), which provides three key layers of protection:

              1. Encryption—encrypting the exchanged data to keep it secure from eavesdroppers. That means that while the user is browsing a website, nobody can "listen" to their conversations, track their activities across multiple pages, or steal their information.
              2. Data integrity—data cannot be modified or corrupted during transfer, intentionally or otherwise, without being detected.
              3. Authentication—proves that your users communicate with the intended website. It protects against man-in-the-middle attacks and builds user trust, which translates into other business benefits.

              Best practices when implementing HTTPS

              Use robust security certificates

              You must obtain a security certificate as a part of enabling HTTPS for your site. The certificate is issued by a certificate authority (CA), which takes steps to verify that your web address actually belongs to your organization, thus protecting your customers from man-in-the-middle attacks. When setting up your certificate, ensure a high level of security by choosing a 2048-bit key. If you already have a certificate with a weaker key (1024-bit), upgrade it to 2048 bits. When choosing your site certificate, keep in mind the following:

              • Get your certificate from a reliable CA that offers technical support.
              • Decide the kind of certificate you need:
              • Single certificate for single secure origin (e.g. www.example.com ).
              • Multi-domain certificate for multiple well-known secure origins (e.g. www.example.com, cdn.example.com, example.co.uk ).
              • Wildcard certificate for a secure origin with many dynamic subdomains (e.g. a.example.com, b.example.com ).

              Use server-side 301 redirects

              Redirect your users and search engines to the HTTPS page or resource with server-side 301 HTTP redirects.

              Verify that your HTTPS pages can be crawled and indexed by Google

              • Do not block your HTTPS pages by robots.txt files.
              • Do not include meta noindex tags in your HTTPS pages.
              • Use the URL Inspection tool to test whether Googlebot can access your pages.

              Support HSTS

              We recommend that HTTPS sites support HSTS (HTTP Strict Transport Security). HSTS tells the browser to request HTTPS pages automatically, even if the user enters http in the browser location bar. It also tells Google to serve secure URLs in the search results. All this minimizes the risk of serving unsecured content to your users.

              To support HSTS, use a web server that supports it and enable the functionality.

              Although it is more secure, HSTS adds complexity to your rollback strategy. We recommend enabling HSTS this way:

              1. Roll out your HTTPS pages without HSTS first.
              2. Start sending HSTS headers with a short max-age. Monitor your traffic both from users and other clients, and also dependents’ performance, such as ads.
              3. Slowly increase the HSTS max-age.

              If HSTS doesn’t affect your users and search engines negatively, you can, if you wish, ask your site to be added to the HSTS preload list used by most major browsers.

              Consider using HSTS preloading

              If you enable HSTS, you can optionally support HSTS preloading for extra security and improved performance. To enable preloading, you must visit hstspreload.org and follow the submission requirements for your site.

              Avoid these common pitfalls

              Throughout the process of making your site secure with TLS, avoid the following mistakes:

              MS Office News

              Microsoft Office 2003 bis Office 365

              Monthly Archives: September 2006

              Outlook 2007: Die neue Aufgabenleiste – Die Zusammenarbeit mit OneNote 2007

              Bereit für einen neuen Tag – Ready for a New Day

              Große Ereignisse werfen lange Schatten. Und sehr große Ereignisse eben noch längere. Der Launch der neuen Microsoft-Produkte Office 2007, Vista und Exchange 2007 rückt immer näher.

              Und jetzt stehen auch die ersten Termine im Netz. Termine für Roadshows und Briefings.

              Die Seite mit den Informationen zur Roadshow und zu den Briefings erstrahlt in einem schönen Rot-Ton, eben wie ein beginnender neuer Tag mit einem schönen Sonnenaufgang.

              Die Veranstaltungen sind mit Referenten bestückt, die Rang und Namen haben. Microsoft hat für die Roadshow wirklich alle Experten zusammengerufen und diese sind dem Ruf gefolgt.

              Fast alle dieser Sprecher haben auch im Netz interessante Blogs mit einer Fülle von Informationen zu bieten und auch Webcasts von und mit ihnen sind sehr zu empfehlen.

              Die Termine für die Roadshow:

              23.11.2006, Berlin
              Clarion Hotel Berlin
              Pandox Berlin GmbH
              Lützowplatz 17
              10785 Berlin

              27.11.2006, Hannover
              Maritim Airport Hotel Hannover
              Flughafenstraße 5
              30669 Hannover

              12.12.2006, Zürich
              World Trade Center Zürich AG
              Leutschenbachstraße 95
              CH – 8050 Zürich

              Die Tagesordnung zur Roadshow und weitere Details findet man unter

              Auf dieser Seite findet man auch die Details zu den Briefings für Unternehmensentscheider und die Details zu den den Behördentagen.

              Der Besuch der Roadshow lohnt sich bestimmt, denn man bekommt nicht nur die neuesten Informationen sondern auch noch Vista und Office 2007 als Final-Version, denn sie sind im Preis inbegriffen.

              OneNote 2007 und das Technical Refresh

              2007 Microsoft Office System Beta 2 Technical Refresh

              Setup fails with Error 2711. An internal error has occurred. (FeatureName)

              This is usually caused by having a previous or newer version of an Office12 product installed on the machine. Ensure all builds of Office12 products that do not match the build numebr of the product being installed are removed from the machine then attempt the install again.

              In some cases it has been found that if a newer build has been run over an older build, that after removal of the older builds there is still data remaining in the registry and the MsoCache from the older build. If this is the case follow these steps to clear out the information:

              1. Open regedit
              2. Browse to HKLM\Software\Microsoft\Office\Delivery\SourceEngine\Downloads
              3. Remove any key that ends in 0FF1CE>
              4. Open C:\MsoCache\All Users 5. Delete any folder that ends in 0FF1CE>-C

              Das ist meistens der Fall, wenn vorangegangene oder neuere Versionen eines Office 2007 (12) – Produktes auf dem Rechner sind. Stellen Sie sicher dass alle Versionen von Office 2007, die nicht die richtige Versionsnummer haben und installiert sind, deinstalliert werden. Danach installieren Sie das TR erneut.

              In einigen Fällen ist es vorgekommen, dass wenn eine neuere Version über eine älter version installiert wurde, die Daten der älteren Version nicht aus der Registry entfernt wurden und auch der MSOCache von der älteren Version war. Ist das der Fall, folgen Sie den unten aufgeführten Schritten um die Informationen zu bereinigen:

              1. Öffnen Sie die Registry (Start –> Ausführen –> regedit)
              2. Suchen Sie folgendes Verzeichnis: HKLM\Software\Microsoft\Office\Delivery\SourceEngine\Downloads
              3. Entfernen Sie alle Schlüssel die mit 0FF1CE> enden
              4. Öffnen Sie C:\MsoCache\All Users
              5. Entfernen Sie alle Verzeichnisse (Ordner) die auf 0FF1CE>-C enden

              I installed the B2TR update for Office Pro Plus. When I try to install Beta2 for OneNote or Visio the install of Beta2 fails with an Error 2711.

              This is a known issue. You should install all the Office products at Beta2 level first and then upgrade each product to B2TR.

              Microsoft Office Compatibility Pack für Word-, Excel- und PowerPoint 2007-Dateiformate (Beta 2 Technical Refresh)

              How to transfer domains in AMP

              Domain transfers can be processed in the Account Management Panel(AMP) for your account. You may transfer the domain yourself by going through our Domain Transfer Walkthrough for beginning users. There is also an Advanced User Option for more experienced users.

              If you seek to move a domain by changing your name servers, or you don’t know the difference, please see Domain Names – Registrar Transfer versus Name Server Change for an explanation.

              Be aware that domain transfer policies have changed. If you update your contact information at your current registrar, there may be a 60-day transfer lock on the domain. You can check the status of your domain by searching whois or checking with the current registrar.

              Domain Transfer Requirements

              Before you can transfer a domain you must meet the following requirements:

              • InMotion Hosting can only support .com, .org, .biz, .net,.us or .info domains. If your domain type is not included in this list, you can still host the domain with InMotion Hosting, but you will need to change your nameservers.
              • The domains must be past their 60 day waiting period after you have purchased them.
              • If your domains are set to expire within 14 days, you will need to first renew the domain with its current registrar. This is required in order to prevent the loss of your domain name in the event that the transfer request fails.

              How to use the Domain Transfer Option in the Account Management Panel (AMP)

              Under the section labeled "Manage My Account" click on the icon that is labeled Transfer Domain

              You will see a list of requirements that fail the transfer if they are not met. Make sure to review these requirements before proceeding. Click on the icon that is labeled Begin Transferring Domain.

              Next you will see the options to transfer the domain by clicking on Begin Walkthrough or Advanced User Option. Click on the button for Begin Walkthrough to proceed.

              The walkthrough begins by asking you to type in the domain name. This option will double-check your domain to see if it is available for transfer. It will check to see if your domain is locked or not. If it is locked, you will need to speak with your domain registrar to have it unlocked. Click on Check Availability.

              This step asks that you review your domain to make sure the domain privacy is turned off. It must be off for the transfer to occur. You can re-apply domain privacy after the transfer is complete.

              If you wish to be able to use the domain with InMotion Hosting immediately upon the completion of transfer, then you need to change the name servers to point to InMotion Hosting. If you are trying to maintain service with your old host for your website and email, then you may want to wait and keep the old name servers in place while the domain transfer completes.

              The next steps require that you obtain your Authorization code (also known as the Extensible Provisioning Protocol or EPP key) from your current domain registrar if you don’t already have it. The process for obtaining the code may differ per domain registrar, but you should be able to either go to their documentation or speak with their support in order to find out how to get your authorization code in order to move the domain. Once you have code, type it in and move to the next step. NOTE: Due to privacy law changes, the WHOIS information is no longer used for the transfer of the domain. At this point you will only need the EPP key.

              Next, you will be presented with the payment part of the process. Complete the payment and then proceed to the final step in the transfer walkthrough.

              As per step 8, you will receive an email from our domain registrar- OpenSRS. The should take no longer than 3 days to be sent. Make sure to check your Spam/Junk mail box in case their email gets flagged as spam. Once you have completed the confirming the transfer, then the domain transfer is complete. Note that it can take up to 10 business days for a domain transfer to complete.

              The Advanced User Option for transferring domains

              The main difference between the Domain Transfer Walkthrough and the Advanced User Option is that the Advanced User Option skips the first three steps. These steps involve removing domain privacy, unlocking the domain, and obtaining the authorization code. These steps are assumed to be completed before you begin the process. Here are a summary of the remain steps:

              1. Confirm access to the Administrator Email
              2. Complete the order transfer form (billing information, payment method, and Terms of Service)
              3. Await the confirmation email, then click on the link provided in the confirmation email that arrives from OpenSRS. The link requests a password, but it refers to your authorization code.

              Congratulations! This completes the domain transfer process. Note that although you have completed the transfer process, it may require up to 10 business days before the transfer is finalized between the domain registrars.

              Leave a Reply

              Your email address will not be published. Required fields are marked *