You have a Mac Computer and are running Microsoft Desktop (RDP) throws an Error code: 0x4 just randomly when you try to connect to a computer you have configured for connection.
For us, this problem just randomly started this year after Microsoft updated their RDP software. “Go Microsoft”
We have searched the web, and noticed that the suggestions to Reboot the computer, or restart the RDP software, or both. Do not appear to reliably work. Although we did have some luck with this.
Another suggestion was to copy or recreate the connection in RDP. Again, only limited success with this solution.
For us the solution came when we went into the system preferences of the Remote Desktop Connection
And you will notice the default preferences look something like this.
We simply unticked the “Use hardware acceleration when possible” check box.
That’s it. After doing this you should notice that it fixes Mac RDP not connecting with 0x4 Errors.
Is why would you want to do such a thing. And usually the reason is that you’ve ever sold the application to a new organisation and subsequently transfer it to their development account. Offer some reason you’re moving it to another account of your own perhaps hundred different name or tax system.
In our example was gonna be transferring it to a new account purely for tax reasons. There is nothing dodgy going on, just legitimate reorganisation of our tax portfolio.
In order to complete the transfer, you’re going to need to have your new account set up and most importantly the new banking and tax details set up for whichever region you live in.
To ensure that these are set up correctly, log into your App Store connect page. And from the list of icons, select the agreements, tax, banking.
Here you can doublecheck that for both your free apps, and paid apps, that the status is showing active for your country and region.
Personally I find it easiest to use to web browser sessions. But that’s in Tiley up to you. I also prefer to do it one application at a time, assuming that you have multiple applications to transfer it can really help if you get bogged down with one to understand why it’s not transferring without getting muddled up with any emails or other notifications from other applications.
Log into the App Store connect with your old account, or the account that you are transferring from.
Select the application from the list of apps, that you wish to transfer. In our example we are going to use the trip tracker app.
From the left-hand menu, select have information.
Then on the right hand pain, scroll to the very bottom.
Look for the transfer app link in the additional information at the very bottom.
You will need to ensure that all of the criteria for transfer are met. There are several common mistakes here that can prevent you from making the transfer. The most common one is that your application relies on the iCloud to store information. You cannot transfer an application while the iCloud feature is enabled within your application. The easy solution for a problem like this, is to release a version that doesn’t use the iCloud feature. Publish this version, transfer the application and then re-publish a new version that adds the iCloud feature back into the application.
Next you’re going to have to fill in the recipients Apple ID. This is the email address associated with the other development account. You will also need the team ID. If you’re unsure where to find this hover on the? To the right and it will explain that it can be found in the developer login under membership.
Next you’re going to have to agree to the terms for the transfer. Scrolling to the bottom and ticking the box before request transfer button.
You are now complete with the old account.
Log into the new App Store connect page with your new account details.
If it has been few minutes since you requested the transfer. You will probably see and yellow message with application transfer request pending acceptance.
It is okay if you do not see this. As you can simply click on the agreements, tax, and painting link.
Clicking this link takes you to a page that will list among other things the applications that are waiting for transfer. It will also include the link to the review section that will need to be filled in to complete the application transfer for the new account.
Click on the review link.
Next you will need to fill in the details that support the applications new home. This includes the support URL, the application review contact information and phone number and email. Then you will need to agree to the terms. Interestingly every time we transfer applications the terms are garbled rubbish that we can’t actually read. And I suspect it’s that way for everybody. However in all honesty who cares, as we would not have read it anyway.
Once you are greeted this transfer request terms. You are done and the application will appear within the new accounts App Store connect page.
Basically this error is telling you that the path in the config.php file is invalid for some reason. The most likely reason being that the http:// is defined and it should be https://
If you open the file config.php in your favourite editor
And navigate to line 21, depending on your version and edits to the file.
You can update your pat URL to include the “s” in https
Save and you should be able to access the site correctly.
So if you are working with Mautic 3.1 like we are as of today, and you are installing modules that connect to the Mautic API, you will find that after you make Custom Fields Editable
Or Enable the API for Mautic in CONFIGURATION / API SETTINGS
That you will then need to clear the Cache directory of Mautic before your other Applications will be able to connect to the API.
Now we are using cPanel and have access in there to the File manager. Easier than running an SSH command is to go into the director: var/cache in the Mautic directory. In our case here we have it in a directory or folder named marketing.
You will see a bunch of files here like this:
Just delete all of these files from the cache folder.
That’s it. You should then be able to connect to the API.
Lets hope that one day Mautic add a clear cache button to the application.
Is the implementation of SSL important for your website? The answer to that is simply YES…
And we are about to list some of the common reasons that SSL encryption on your website is more important than ever.
But first, let’s explain exactly what SSL encryption is…
Putting is simply, is is when you access a website using HTTPS:// before the address in place of HTTP://.
Websites that use https:/// are using some cleaver encryption that ensures that information sent to the website browsers and from the website browser to the website is secured and cannot be intercepted by people spying on your connection.
Sites without this encryption send information back and forth as plain text. Making it super simple for anyone who is looking at this information to read all of it.
This includes passwords (and we all know we use the same passwords on different sites), to personal information such as when filling in a form. Email Address, Date of Birth, Address, Phone Numbers etc are just some of the information we want to ensure remains secure.
Since 2018, when Google made SSL/TSL mandatory. Most web browsers such as Chrome, Firefox, Edge will throw warnings to customers who try and access your websites.
Some warnings are subtle, but others can be quite significant and you may not be aware of this if you are not using the same browser and computer system as your customers.
The above image is some of the examples of warnings that your customers can get from your website when it is not secure.
We actually see the removal of user warnings as the Number 1. Reason to implement SSL on your website.
Way back in 2014, Google made changes that included SSL in the algorithm for search engine rankings.
So simply put… your site will rank better with SSL that without, and subsequently you can expect more people to browser your site.
There have been many studies that confirm that. One of these studies is by backlinko.com.
So SSL helps you get to the First Page of Google. Something everyone wants in their industry.
The entire reason that Google gives better rankings for sites with SSL/TSL encryption, and the reason that they throw warnings to users who visit sites without this encryption is that they are encouraging all of us to be secure with Data.
SSL will help protect your site, and your users data from the huge army of users who try to attack it on a daily basis. Many of our customers and web users would not be aware of just how prolific hacking is and how real the threat is.
Our website Interactivewebs.com for example receives around 7000 hack attempts a week. If one of these hack attempts are cleaver enough, and your site is not using SSL, then it is not too difficult with freely available hacking tools to gain data such as passwords entered as a user logs into your site.
Adding SSL to your website makes the monitoring of passwords and other information almost impossible.
Many Countries like Australia, Europe, UK, and the USA all require that people taking payment on the web comply with PCI / DSS standards.
One of the core functions of taking payments on a Website is to do it in a way that does not put the user of the site at risk of theft of their details.
Using SSL/TSL security is a cornerstone of encrypting data for your website users. In most first world countries, this is a legal requirement and the PCI DSS standards are used as a minimum standard for web security for sites that take payments.
Building Trust in your Brand is important. Sometimes with customers this is something that you can build over time.
For Web users, the experience of trust starts with the first Impressions.
Security on a Website with SSL is the first point that customers make judgments about how seriously you take security and how they will trust you with their data.
If you throw a security warning to every Firefox user who hits your site, then you are starting the user experience saying you do not value their data.
Simply the trust in your brand start from a position of mistrust if you are not using SSL.
One of the most important processes of implementing SSL on your Website is the validation of Domain Ownership.
This step proves that the SSL certificate that has been implemented is part of the Brand, Company and Domain that is using the certificate.
This is the second primary task for the SSL implementation, and although we rank it in 6th place, it could be argued that it is super important as it proves to users that your site is “real” and not someone else pretending to represent your company.
We take care of this validation process on your behalf when we implement SSL on your site.
Adding SSL Security to your InteractiveWebs hosted website has never been easier.
Place the order with us, and we will implement everything for you.
NOTE: For existing customers. If you have not logged into our client system before, please use the “Forgot Password” function to retrieve your login details.