Martin A.

1: Only FontAwesome 4.7 is supported by the Invision Community Suite. Docs are here: https://fontawesome.com/v4.7.0/icons/
fa-plane-arrival is sadly not available in that version.
2: That is imported from a task that runs once a day. You can either locate the list of tasks, then run the one that belongs to "Member Map" manually, or wait till tomorrow 🙂 

That would not be possible with this map. Looks like you need an app, or just an open web page, that the bus driver has to keep updating his position, and a map page that periodically updates to show the last known location for all buses and their routes. Would need a custom app for that.
All you did was upload the .tar file you downloaded from the marketplace, right? Are you able to install other apps? Have you verified the directory permissions as stated in the error?

Thanks Martin, both are working properly now

1: Only FontAwesome 4.7 is supported by the Invision Community Suite. Docs are here: https://fontawesome.com/v4.7.0/icons/
fa-plane-arrival is sadly not available in that version.
2: That is imported from a task that runs once a day. You can either locate the list of tasks, then run the one that belongs to "Member Map" manually, or wait till tomorrow 🙂 

Interesting, what type of issue did you have? I've been using AWS S3 with Cloudflare using Full Strict mode without any problems. I use it for Theme files too, taking 1000's of Requests off my server every hour and bringing the Theme files closer to my international visitors.
Re the brief discussion on Public access to files (Astrapi addressed this in his excellent guide)
In general it's a really bad idea to make your files public on S3, I'd definitely recommend keeping them private whilst permitting/restricting access via IAM permission policies and API Keys.
Amazon have really increased awareness of this when you look at the s3 bucket configuration console, but in there documentation there are still outdated references to be found stating you have to make bucket content public when actually you don't and shouldn't. It's true that 99% of your stored content is going to be everyday pictures of cute cats and hot cars etc but it makes sense to also consider the impact, cost and repercussions of someone directly accessing say, a list of passwords and authentication details shared between staff, or photos uploaded to private gallery albums containing EXIF gps coordinates identifying where a photo was taken. 
If you keep your files and bucket restricted with no public access, you help reduce and mitigate risk. Some quick examples here would be:
you don't have to be as concerned about potential security issues (confidential documents or images uploaded as attachments in price forums or PMs, for example), you help maintain higher GDPR compliance (both with the principles of the GDPR and Data Protection legislation and in terms of complying with your site's published GDPR policy),  and you help negate the risk of people or bots finding and publishing direct URLs to your content and therefore being able to bypass your CDN entirely which poses an escalated risk of higher monthly S3/CDN usage costs, potential for DDoS attacks from a financial attack vector rather than aimed at taking down your site etc. Wasabi, don't get me wrong and I have nothing against it and haven't yet used it myself, is attractive price-wise, but its cost saving is relevant to your individual usage case. S3 is already very low cost, especially if you front it with a CDN like Cloudfront, Cloudflare or both, so 80% of little becomes quite little. Unless you are storing and accessing massive amounts of data, the difference in cost against AWS S3 could be almost negligible for the average IPS community, a few cents or maybe a dollar or two. 
Plus when you start looking at Wasabi's documentation, it becomes apparent that there are some services and functionality that they don't provide or that are planned for a future date. If you a bit of a performance nut enthusiast like me and want to attain increased or 100% Pagespeed ratings, some of those services may become more relevant and necessary to you. For example, if you are going to self host webfonts like Google Fonts, Icomoon and Font Awesome to get to that 100% rating, or you (hopefully) have a good Content Security Policy set up, your are definitely going to need CORS headers.
https://wasabi-support.zendesk.com/hc/en-us/articles/360006985652-How-do-I-use-CORS-and-custom-domains-with-Wasabi-
Again, I'm not intending to distract or diminish Wasabi, just highlighting that there are possibly additional considerations for some IPS communities more than others and that AWS have lots of extra tools, bells and whistles.

Glad you got it working. Setting the policy did ring a bell, I remember doing something in that area, but not sure what.
The background queue MOVES the files.

@yevlem Could it be that your DNS changes haven't propagated yet? It may take a while for a nameserver change to be picked up by the various DNS servers around the net. Most take up to 24 hours.
If you visit https://cdn.mysite.com, are you getting something?

Had a speak with @ASTRAPI, and he can't remember how he did it, but he's going to check it out when he's back behind the computer.
Maybe @The Old Man remembers how he did it?

Hi,
This could be done sort of easily if you add a new "Address" field to your database. I could then expand on the existing Calendar feature to also look up articles that are geolocated. Let me know if this is doable for you.

Hi,
I'll look into this, but won't make any promises right now.
Can already be done by editing the permissions for each marker group.

What @iacas wrote above is correct.
The days of zipped downloads is over, and you’ll see others devs do the same with their apps and plugins in the future. @Daniel F have asked us to stop doing that unless we have a good reason, as it apparently led to confusion to some clients that tried to upload the .zip/.rar to the ACP.

So, I got this to work! It's quite simple actually.  Thank you to whoever created the tutorial.  A few gotchas: make sure to set CloudFlare to Full, if you do Full(Strict) you will get the SSL error that I described above. Also, make sure to use https:// in your CDN url. Other than that it's working great so far. 

@ASTRAPI is helping me move my community over to Wasabi and Cloudflare.  
For any Invision Communities who are currently using Amazon S3, then you may want to seriously investigate the pricing for Wasabi or other S3 compliant services.  Wasabi is significantly cheaper (80% cheaper), charges nothing on exit bandwidth, and compatible with CloudFlare.  It's a drop-in replacement for S3, so for purposes of your ACP, you would treat it like an Amazon S3 storage.  

Hello
(This is a community guide on how to setup Wasabi and Cloudflare, as a significantly cheaper replacement for Amazon S3 and Cloudfront.  The author has no affiliate arrangement with any of the companies listed in the guide and offers the guide as a free community resource.  You should consult with your hosting provider and / or server administrator before proceeding with the guide.)
BACKGROUND:
Invision Communities contain rich content, from forum attachments to gallery images to download files.  These resources add up over time. 
Here are real examples of communities that I provide server administration for:
- Website A: 400 GB of total storage and 1.2 TB of total monthly bandwidth 
- Website B: 800 GB of total storage and 14 TB of total bandwidth
Invision Community allows a file storage configuration with Amazon S3 and a content distribution network (CDN) of your choice:
 
WHAT IS WASABI?
Wasabi Cloud  is faster and cheaper than Amazon S3 for object storage, offers unlimited egress for bandwidth, and compatible with Cloudflare.  One of the biggest hidden expenses of using Amazon S3 is not the cost of storage itself, but the bandwidth to deliver objects in and out.  Wasabi does not charge for egress bandwidth, which can save on the majority of the true cost of Amazon S3. It also provides an S3-compliant interface, which means it can be used as a perfect drop-in replacement for Amazon S3 storage and immediately usable on all Invision Communities.   

Wasabi is 80% cheaper and 6x faster than Amazon S3, with 100% data immutability protection, and no data egress fees or API charges. Created by Carbonite co-founders and cloud storage pioneers David Friend and Jeff Flowers, Wasabi is on a mission to commoditize the storage industry. Wasabi is a privately held company based in Boston, MA.
In March of 2018, Wasabi pioneered the cloud storage industry’s first ‘unlimited free egress’ pricing plan. We are excited to join forces with Cloudflare and the Bandwidth Alliance, validating that the early business models of Cloud 1.0 vendors no longer applies in a world that expects unlimited everything.  What this means in practice is that you can use Cloudflare services (including the free plan) like blazing-fast DNS, WAF firewall, performance improvements on the fly, and much more.  Forums users will request a topic, and all static content can be picked up from Cloudflare's optimized services that will connect to Wasabi.

 
At the moment, Wasabi offers three Datacenters:
1)US-WEST
2)US-EAST
3)EU-CENTRAL 

One price. Lightning fast speed. No hidden fees.

You can check and compare the prices above.
 
GUIDE:
BEFORE PROCEEDING, PLEASE BACKUP YOUR DATA FIRST!
YOUR FILES WILL BE IN PRIVATE MODE AND WILL NOT BE ACCESSIBLE ON YOUR FORUM !
YOU MUST GET A PAID PLAN TO BE ABLE TO ACTIVATE THE INVISION FILE PERMISSIONS AND GET YOUR FILES ACCESSIBLE AT YOUR FORUMS.
JUST ADD YOUR CREDIT CARD NOW (AT YOUR PROFILE PAGE) AND THEY WILL CHARGE YOU 5,99$ FOR A MONTH FOR 1TB STORAGE AND UNLIMITED BANDWIDTH.
THE FREE TRIAL WILL NOT WORK FOR INVISION !
 
Step 1: Create a CName at CloudFlare
We start by creating a cname at Cloudflare:
cname -> cdn -> cdn.yourdomain.com.s3.eu-central-1.wasabisys.com  <--For Europe datacenter
or
cname -> cdn -> cdn.yourdomain.com.s3.us-west-1.wasabisys.com  <--For US-WEST datacenter
or
cname -> cdn -> cdn.yourdomain.com.s3.wasabisys.com  <--For US-EAST datacenter
Like this:

 
Step 2: Create a bucket on Wasabi
First we sign up for a free account at Wasabi Cloud: https://wasabi.com/sign-up/
Then we create a bucket:

 
It is important to name it as: cdn.yourdomain.com
 

 
Then keep default suspend Versioning and Suspend Logging:

Then click CREATE BUCKET:
 

 
Step 3: Retrieve your Access Keys
Go to the menu on top left and click Access keys on the left. Click on "Create New Access Key."

 
Copy / save the access key and the secret key:

Step 4: Setting up a new file storage in ACP
Login to Admin Control Panel and navigate to Overview at the Files category and then click at the right side at Storage settings:

 
Then we click at Configurations and at the right side at Create New:
 

We select Amazon s3 and we add the following info:

Save it.
Step 5: Set the new storage at storage settings
Navigate to Storage settings and select from the drop down menu the new Amazon s3 bucket.

 
Keep only at your server your theme resources:

*Attachments and Downloads doesn't work out of the box as it seems there is some hardcoded code at Invision related to S3...
To make them work you just need to install the addon bellow: (tested with Invision 4.4.4).
 
Then wait for any Invision background tasks to finish and check.
I hope that you will benefit from this tutorial and get better performance while saving a lot of money 🙂
Enjoy!
OTHER NOTES:
If you are already using S3 then it is very easy to move straight to Wasabi by following the above tutorial as it is NOT needed to move back your files to server and then to Wasabi.
CREDITS
Credits to @Joel R for giving me the motivation to write this tutorial and providing screenshots from his Wasabi account and for editing the topic.
Thank you

it was my browser sorry

The updated version was posted on Tuesday. 
 
@JohnDar Thanks, I’ll look into that. 

I just downloaded it and the downloaded file WAS a .tar file.
Maybe stop your browser from auto-expanding the download?

I just uploaded a patch now that should fix that issue.

After. Same with all other apps and plugins. 

The updated version was posted on Tuesday. 
 
@JohnDar Thanks, I’ll look into that. 

A 4.4 version will be released soon, with the possibility to add a marker as a guest.

A 4.4 version will be released soon, with the possibility to add a marker as a guest.

A 4.4 version will be released soon, with the possibility to add a marker as a guest.

I use it on one of my sites with 4.4. Works fine for me..

No, I have not. A pull request is a way for people to contribute with code changes to a repository, where you would develop the requested feature(s), and hand it over to the repository and the rest of the community.
I've mentioned several times in this topic that I do not have time to add new stuff to this app at the moment.