- Multimarkdown Composer 4 Pro 4 5 12 Volt
- Multimarkdown Composer 4 Pro 4 5 12 Amp
- Multimarkdown Composer 4 Pro 4 5 12 Battery
- Multimarkdown Composer 4 Pro 4 5 12 Days Of
- Multimarkdown Composer 4 Pro 4 5 12 And 33 42
- Multimarkdown Composer 4 Pro 4 5 12 Commentary
Issue on macOS 10.11 with MMD Composer 4.5.12: MultiMarkdown Composer 4 Pro Upgrade: Advanced Preferences: Using various cloud services with Composer for iOS. Drive composer pro 1.3.0.0 Readme file (English - txt - Instruction) Drive composer entry 1.0.5.0 readme file (English - txt - Instruction) Drive composer pro 1.2.1.0 Readme file (English - txt - Instruction) Edgeport/1 not working on USB 3 ports (English - pdf - Instruction) Drive composer entry 1.0.4.0 Readme file (English - txt - Instruction).
Composer Icon
Product: MultiMarkdown Composer v4
Price: Free, Standard Edition: $14.99, Pro Edition $29.99
Price: Free, Standard Edition: $14.99, Pro Edition $29.99
In the crowded field of Markdown based text editors, MultiMarkdown Composer (Composer) is a differentiated beast. For one, it is based on MultiMarkdown or MMD. MMD is a superset of the Markdown syntax, originally created by John Gruber. It adds multiple syntax features (tables, footnotes, and citations, to name a few). In addition, it outputs to various formats including HTML, PDF (by way of LaTeX), OPML, or OpenDocument (specifically, Flat OpenDocument or ‘.fodt’, which can in turn be converted into RTF, Microsoft Word, or virtually any other word-processing format). The original Markdown only outputs to HTML.
iA Writer is another product which supports MMD, with a few tweaks.
Secondly, Composer is designed for more than the individual document creation that most of the minimalistic Markdown based writing applications specialize in. This is an application which lends itself to the production of long form documents with images, tables, footnotes and citations if you so wish. It includes math support, automatic cross-referencing, glossary entries(LaTeX), and document metadata when you need it.
Conceptually, Composer is a Markdown based text-editor for writers who want to go beyond the constraints of the Markdown designed by Gruber.
If you look at the market of text editors, the two main categories were:
- Full featured text editors like BBEdit, Sublime Text 3, TextMate, and Atom. These products through extensions and plugins have the ability to handle every flavor of Markdown that you can throw at it. These are capable but complicated beasts.
- Minimalistic Markdown based text editors like iA Writer and Byword. These products support a subset of the functions of a text editor. Geared for writing Markdown, they concentrate on providing an optimized environment for writing in Markdown syntax with keyboard commands and syntax support being the focus.
We have a new category populated by MultiMarkdown Composer. With keybindings, macros and completions, Composer is in the middle of the two categories. Not as feature rich as the archetypical text editor, but not as feature deficient as the minimalistic text editor. With a detailed system of preferences, support for MathJax and CriticMarkup, text completions, and keybindings, Composer is positioned between the two extremes. The only competitor who might challenge Composer is Typora when the later comes out of beta. However, the wait for that seems interminable.
Changes in the Workflow
Readers of the blog know that my workflow consisted of writing and editing in iA Writer and managing files in Sublime Text 3. There have been two changes to the workflow. I have given up on managing my text files through a text editor. Don't need that. The Finder does a good job of that. So, iA Writer became the mainstay of my writing. It is a great Markdown based text editor. But Composer is better at certain things and has now joined the workflow. I now write in Composer and the final edit is done in iA Writer.
Composer provides the following advantages over iA Writer:
- Composer deals with multiple open files. Thanks to its support of the system tabs feature, I can have multiple documents open in tabs in a single window. Reduces clutter and makes it possible to have multiple documents easily accessible.
- Composer is more extendible than iA Writer. In fact, iA Writer by design is not extendible at all.
- Composer supports CriticMarkup.
- Composer supports Table of Contents (TOC) in its sidebar. This makes navigation simpler for large documents. Makes it possible to change the order of sections in documents by dragging and dropping sections into the desired order.
- Typewriter scrolling can be set for the spot you desire. iA Writer doesn't let you customize this.
- Text expansions make it possible to write with less effort.
- Composer keybindings let you make changes to existing keyboard commands and add your own keyboard commands.
- Theme support makes available other options beyond dark and white.
What are the advantages of iA Writer over Composer?
- One program. You can both write and edit here. Living in one program has certain advantages.
- Narrower focus. Which means a shorter learning curve.
- Editing component. Grammar check helps people like me write a tad better.
- Less options necessarily means less tweaking.
- Swiping to access the directory structure and preview is even easier than keyboard commands.
So, I switched the writing function to Composer. I have been writing in it for about a month now and I must say that I am falling in love with the application. It feels like an application designed by a writer of Markdown. And it is. Fletcher Penny the developer is also the man behind MultiMarkdown. He designed the markup language with inspiration from Gruber and he wrote the application MultiMarkdown Composer to write in it. There are little touches across the program which make it easy to write in Markdown and it is a pleasure to live in.
What Makes Composer Special?
What does MultiMarkdown Composer version 4 bring to the genre of Markdown based text editors that make it special?
Live Preview
You get to see the output of the file you are working on in real time. For those of you who are new to Markdown, this will show you exactly how your finished output will look. You can use custom CSS for the preview. Additionally you can turn off the MultiMarkdown Composer preview and use Marked 2 for previewing your document.
Themes
MultiMarkdown Composer supports themes and ships with a collection of themes. You can learn how to customize or create your own themes at MultiMarkdown Composer v4 Themes.
You can also go to my github repository of Composer themes, to download the initial work in progress on an iA Writer Dark and Light theme. I am going to post themes in this repository as I finish working on them. Keep a lookout for those.
Math and Other Esoteric Elements
Built-in linking to MathJax or syntax highlighting javascript libraries to improve the quality of your web preview.
Smart Pairs
When you type the first part of the syntax for Markdown, the application automatically completes the pair. You can also select text and type the first character of the Markdown syntax and the application surrounds the highlighted text with your Markdown code.
Elastic Tabstops
This is difficult to explain, so, I am going to quote from the MultiMarkdown Composer website:
'Years ago, Nick Gravgaard created a project that provided better tabstop support for certain editors, and that concept is supported in MultiMarkdown Composer. Rather than assigning a fixed number of spaces to a tab character, or a fixed width, tabs represent “columns” of text. Contiguous lines of text are examined to ensure that the columns are wide enough to contain the text in each line. This allows you to easily see your text the way it is meant to be seen, regardless of whether you use a monospace or proportional font.'
You can learn more about Elastic Tabstops.
Easy Line Shifting
Menu commands with assigned keyboard commands lets you move highlighted lines of text up/down/left/right.
Easy Line Shifting
Conversion Between Markdown Block Types
I don't think any of the other Markdown editors do this.
Markdown Block Type Conversions
You can take any text and easily add or remove Markdown markup. You can convert any instance of Markdown formatted text to Blockquote, or a Ordered List or an Unordered List, and so on. A convenient and useful feature.
Clean Up Imported Text
Composer has a slew of commands you can use to clean up text, as well as commands to clean up the formatting of Markdown and MultiMarkdown structures. This is another feature which I haven't seen in any other Markdown editor.
Clean Up Imported Text
Automatic Formatting
Composer helps you write by providing some formatting help. If you are writing an ordered list, Composer takes care of the numbers. If it is an unordered list, the bullets are taken care of by Composer. Have a link on the clipboard? Highlight the word you want to attach to the link and press ⌘V. Turns into a formatted Markdown link.
TOC Sidebar
Composer generates a Table of Contents (TOC) sidebar from the headings in your document. Clicking on a heading takes you to that section in your document. You can search/filter based on content of the heading. Most importantly, you can drag and drop headings in the TOC sidebar to rearrange your document. Reminds me of Scrivener and its Binder.
Preferences Galore
Composer goes against the accepted ethos of minimalistic text editors in its handling of preferences. Most of the competition strive, sometimes going to extraordinary lengths, to keep its preferences to a minimum.
ByWord Preferences
The logic being that if you give writers things to tweak, they will tweak things and not write. Composer shows a lot more respect to writers and gives you a full set of preferences to tweak and set up your text editor the way you want. It is a window into two facets:
- Composer supports MultiMarkdown and the MultiMarkdown specification is more comprehensive than Markdown.
- Composer is designed for the 'serious' writer. And various incantations of said 'serious' writer. It supports MathJax, and syntax highlighting for code on the one hand and then also supports CriticMarkup, and Table of Contents (TOC) on the other. It is a full-featured writing environment and not just a sheet to write a blog post in. The technical writer can use it to write github readme files and the non-fiction science writer can use it to write journal articles. The blogger can write in it and the novelist can write in it. The target audience is broader for Composer than its immediate competition.
Use Your Own Theme, Font and Typewriter Scrolling Point
Theme, Font, Typewriter Scrolling Point
Composer supports themes and you have the ability to control fully the user experience of writing in it. Two things I would like to point out that I am fond of. Composer lets you use your own font. I appreciate that. I like writing in DuoSpace and having that accessible to me in my text editor makes me happy.
Composer gives you the ability to specify where exactly you want the typewriter scrolling to be situated on the page. Most applications stick it in the middle. Ulysses gives you a variable spot and Composer lets you choose the exact spot you are comfortable in. Makes it a pleasure to write in.
Typewriter Scrolling Point
Smart Pairs and Title Case Capitalization
The editing preference pane shows some nice features. Smart pairs lets you type the opening character of a pair and the application completes the pair. This is something I have in Sublime Text 3 but don't have in the minimalistic Markdown editors like iA Writer or Byword. Composer also lets me apply 'Title Case' capitalization to headings automatically, giving me one less thing to worry about.
Smart Pairs and Title Case Capitalization
Adopt MultiMarkdown or Stick to Original Markdown
Composer lets you choose to stick to the Original Markdown specifications when you are writing or adopt the full suite of MultiMarkdown.
MultiMarkdown or Plain Old Markdown
Choose Your Syntax
You get to, in Composer, choose the nature of the syntax you want to use for bold, italic, list markers and specify the behavior of tabs. Lets you stick to the syntax you are used to and not dictate a syntax to you.
CriticMarkup Support
CriticMarkup was designed and developed by Gabe Weatherhead and Erik Hess with a lot of help.
CriticMarkup Support
CriticMarkup is a way for authors and editors to track changes to documents in plain text. As with Markdown, small groups of distinctive characters allow you to highlight insertions, deletions, substitutions and comments, all without the overhead of heavy, proprietary office suites.
Having it included in Composer makes it accessible and usable. It is a great system for tracking changes and incorporating editor comments.
Using Marked 2 and Synchronized Scrolling
Having the ability to use Marked 2 to preview the document is much appreciated. The built in preview is great but for those of us who use Marked 2, the integration with it is a favorite feature.
Marked and Synchronized Scrolling
Another feature which I am fond of is Synchronized Scrolling. Specially useful in long documents, it helps to be able to see the finished document exactly where I am editing.
You have the option of adding headers and footers when you are printing your document. Makes the final printout look professional and neat.
Footers and Headers
Auto Save and Versions Support
Composer auto-saves your documents. So, that is one less thing for you to be worried about.
Auto Save and Versions Support
Along with auto-save, Composer supports the built-in macOS feature of Versions. That gives you the ability to go back to any state of the document you prefer. This is a feature it shares with iA Writer.
Expansions
This is the kind of feature which shows the developers intention with the product. TextExpander is an application which lets you type in little snippets which get converted into stock text you have set up. It is a product which is probably the market leader in its space. It has the added advantage of being cross platform. Supported on both macOS and iOS it makes it possible for you to have the same expansions on all your devices. Composer introduces its own implementation of text expansion. It is not as full-featured as TextExpander but it lets you share expansions between devices (when MultiMarkdown Composer comes out with its iOS iteration). Another feature which is unique to Composer.
I use basic expansions from Alfred and detailed or form-filling expansions from Keyboard Maestro. I am looking forward to building my own expansions in Composer to increase my productivity when I am using it.
Text Expansions
KeyBindings
This is another feature which distinguishes Composer from the rest of the competition. Custom Key Bindings and Macros gives you the ability to string multiple actions together into one keyboard command. Through tweaking the .json files, this feature lets you change the default keyboard commands built into the application. It also lets you add your own commands which are not built into the application. To get a basic idea of what is possible in Composer, check out this github repository.
History Mode Undo
Composer goes beyond the system undo feature giving you something it calls History Mode Undo. History Mode Undo allows you to move backwards and forwards even if you typed something new in the meantime. In other words, it keeps all changes to the document until the document itself is closed. This is a great feature when you are editing your document.
History Mode Undo
Pricing
The pricing of Composer is explained here.
Basically, the free version is somewhat hobbled. The Standard version removes these constraints and the Pro version includes automatic text expansion, custom keyboard shortcuts and custom macros, the ability to share configuration files, History Mode Undo and the ability to limit depth in the TOC.
Areas of Improvement
Composer is a mature product which makes writing in MultiMarkdown a breeze. However, it still has some areas it can improve:
- Give us a menu choice and a keyboard command for footnote. Even a completion macro will suffice. (Update: Fletcher Penny, the developer addressed this with Key Binding To Insert Footnote at End of Text. Thank you.)
- The help files need to be updated. There are elements presented which are not there in the application any more. For instance, the Assistants Preferences.
- Built in the grammar checking that iA Writer uses.
- History Mode Undo needs to have an UI to be perfectly usable.
Recommendations
This is the best Markdown based text editor in the market. If you are looking for a full-featured tool to address your text editing needs and you live in Markdown, you need to consider this product.
If you are not particularly geeky and are happy to avoid excessive customization, the Standard edition should suffice. But if the idea of total customizability along with History Mode Undo strikes you as features which you want to explore the Pro edition is recommended.
The developer provided the author with a free Pro edition for efficient bug-hunting during the beta phase of this product.
Composer is recommended without reservations. It is the editor I live in.
macosxguru at the gmail thingie
Previous post
Be Kind. Stop with the Leather Sleeves.Leather Sleeve for 12‑inch MacBook - Saddle Brown - Apple Why? Why do we need to skin animals to make sleeves for our gizmos? You want to create aNext post
Favorite Mac Applications for 2017I am going to cover some of my favorite applications of the year 2017. I am primarily a writer, which means that the bias of the focus will be onForum Navigation
Forum breadcrumbs - You are here:ForumControl4 Composer Pro: Cracking Composer 2+Definitive Composer and Director …
Please Login or Register to create posts and topics.
**Updated 6/3/20 to include 3.1.3 (only one change from below instructions)
**Updated 1/26/20 to include 3.1.1/.2 install and changes
**The guide now has a section broken out for the 1 Yr Cert Renewal and another for controller registration
**The guide now has a section broken out for the 1 Yr Cert Renewal and another for controller registration
Common commands and information.
Default Controller User and Pass:
Username: root
Password: t0talc0ntr0l4!
(3.1.1/.2+ NOTE - Once Composer connects to the controller, the password will automatically be changed. Details below.)
Default Controller User and Pass:
Username: root
Password: t0talc0ntr0l4!
(3.1.1/.2+ NOTE - Once Composer connects to the controller, the password will automatically be changed. Details below.)
Commands to add root user and password:
Command to add new user: adduser USER
Command to change password: passwd
Composer 3.1.1/.2+ is slightly different than previous versions. - Run Composer and when the Controller selection box comes up, right click on the controller and it will bring up a box to start a Terminal session. You need to change the root password so that you can SCP the clientca-prod.pem file to the controller. Type 'passwd' then enter a new password. You now have root access with a password. **NOTE: After you connect to your controller via Composer 3.1.1/.2+, the root password will be removed so this step must happen any time you need to SCP to the controller to update the clientca-prod.pem certs. Or, set up a new user with root access. Details below.
Command to add new user: adduser USER
Command to change password: passwd
Composer 3.1.1/.2+ is slightly different than previous versions. - Run Composer and when the Controller selection box comes up, right click on the controller and it will bring up a box to start a Terminal session. You need to change the root password so that you can SCP the clientca-prod.pem file to the controller. Type 'passwd' then enter a new password. You now have root access with a password. **NOTE: After you connect to your controller via Composer 3.1.1/.2+, the root password will be removed so this step must happen any time you need to SCP to the controller to update the clientca-prod.pem certs. Or, set up a new user with root access. Details below.
Adding permanent root user access:
Type adduser USER with USER being the name of the user you are creating. Enter your chosen password. Verify it.
Normally you could use the usermod command but it isn't available. So edit /etc/passwd
Look for the line with the user name you just created.
user:$kdlskfj.$dklj.$jklj/:XXX:XXX:Linux User,blahblahblah. Change whatever number is in both XXX spots to 0:0.
user:$kdlskfj.$dklj.$jklj/:0:0:Linux User,blahblahblah
Save the file. Reboot.
You now have a new user with root access
Type adduser USER with USER being the name of the user you are creating. Enter your chosen password. Verify it.
Normally you could use the usermod command but it isn't available. So edit /etc/passwd
Look for the line with the user name you just created.
user:$kdlskfj.$dklj.$jklj/:XXX:XXX:Linux User,blahblahblah. Change whatever number is in both XXX spots to 0:0.
user:$kdlskfj.$dklj.$jklj/:0:0:Linux User,blahblahblah
Save the file. Reboot.
You now have a new user with root access
Hey guys, I just threw this together so it would be great if you can provide comments or information to make sure it's correct. I've placed the correct files in the download.
Definitive Install Guide
Items Needed:
Composer 2.5.3
Composer 2.5.3 Composer.exe (cracked) 'Special Exe'
Certs (ca.pem and ca_cert.pem)
Composer 3.1.x (Composer 3.1.1/.2/.3 has some slightly different instructions)
MeeKah Composer Patch (No longer needed in 3.1.x)
Director Patch (Just the clientca-prod.pem certs which have been extracted in the below zip file) (No longer needed in 3.1.x)
C4_Cert_Replacement_Patch
C4_Device_Image_Updater_V2
WinSCP
Composer 2.5.3
Composer 2.5.3 Composer.exe (cracked) 'Special Exe'
Certs (ca.pem and ca_cert.pem)
Composer 3.1.x (Composer 3.1.1/.2/.3 has some slightly different instructions)
MeeKah Composer Patch (No longer needed in 3.1.x)
Director Patch (Just the clientca-prod.pem certs which have been extracted in the below zip file) (No longer needed in 3.1.x)
C4_Cert_Replacement_Patch
C4_Device_Image_Updater_V2
WinSCP
If someone can upload or link the files above, that would be great.
A Helpful link:
For a quick way to search for Drivers without going into Composer you can go here:
http://drivers.control4.com/solr/drivers/browse?q=
For a quick way to search for Drivers without going into Composer you can go here:
http://drivers.control4.com/solr/drivers/browse?q=
All User Manuals are now accessible through Composer 3.1.x
****UPDATED TO BRING 1 YR CERT RENEWAL TO ITS OWN SECTION****
1.Make sure you have Composer 2.5.3 installed.
2.Rename 2.5.3 Composer.exe to a backup (Composer Bak.exe) then copy the 'Special Exe' Composer.exe into the directory. Run Special Composer.exe. Fill in email and password. Click OK.
2.Rename 2.5.3 Composer.exe to a backup (Composer Bak.exe) then copy the 'Special Exe' Composer.exe into the directory. Run Special Composer.exe. Fill in email and password. Click OK.
If email and password form doesn't come up when you start Composer, delete composer.p12 from the AppDataRoamingControl4Composer folder and re-run or re-copy over the Composer 2.5.3 Composer.exe (cracked) 'Special Exe'. Run Composer.exe. It should come up at this point and is needed to update one of the cert files. Verify that (ca_cert.srl, composer.p12 and openssl.conf) files have been created and updated. composer.p12 is the file which needs to be generated every year and this is how you update it.
*****Register Controller****
You can register your controller in 3.x with a couple of ComposerPro.exe.config changes. These may also work in 2.10 but I never tested.
Changing ComposerPro.exe.config (3.1.1/.2/NOT .3):
Under Web change:
key='LicensingURL' value='false'
key='DealerAccountLocatorURL' value='false'
Under Web change:
key='LicensingURL' value='false'
key='DealerAccountLocatorURL' value='false'
Changing ComposerPro.exe.config (3.1.3):
Change from 'string' to '0' (zero) this line
'ComposerPro_LicensingService_Licensing' serializeAs='0'
Change from 'string' to '0' (zero) this line
'ComposerPro_LicensingService_Licensing' serializeAs='0'
This change allows you access to Account Services, where you can register your controller, and bypasses the initial login dialog. By changing this config, there is also no need for MeeKah Patch.
***Install Guide****
Starting out, and for hygiene, do the following:
- Uninstall all versions of ComposerPro/HE/etc.
- Remove Control4 Directory in - Program Files (x86)Control4 or C:Program FilesControl4
- Remove Control4 Directory in - UsersxxxxAppDataRoamingControl4
- Uninstall all versions of ComposerPro/HE/etc.
- Remove Control4 Directory in - Program Files (x86)Control4 or C:Program FilesControl4
- Remove Control4 Directory in - UsersxxxxAppDataRoamingControl4
That should be all you need to 'start fresh'.
1. Install Composer 2.5.3 (Do not run yet.)
2. Copy Cert files ca.pem and ca_cert.pem to AppDataRoamingControl4Composer folder
3. Go to 'Program Files (x86)Control4Composer253' Rename 2.5.3 Composer.exe to a backup (Composer Bak.exe) then copy the 'Special Exe' Composer.exe into the directory. This special Composer.exe will be the one that causes the ca_cert.srl, composer.p12 and openssl.conf files to be created.
4. Run the Special Composer.exe and you will be presented with a login dialog box. Type in an email and password (it doesn't matter what they are) and submit. (You should check to make sure the files, I mentioned above, show up in the AppDataRoamingControl4Composer folder). If the composer.p12 file is not created, recopy the Special Exe and rerun.
5. **Edit - The Director Patch isn't used any longer, so please use the following steps instead. They always work. If you are using 2.10 or earlier use the Director Patch clientca-prod.pem (Step 5b). The cert you need, clientca-prod.pem, is already extracted and located in the download of this post. If you are using 3.x use the ca_cert.pem certs (Step 5c).
***Use WinSCP to copy over clientca-prod.pem to your controller.
***Use WinSCP to copy over clientca-prod.pem to your controller.
Open Director Patch Folder
5a. WinSCP into the Controller (Director)
- Use WinSCP to connect to Controller via SSH - Use SCP type connection
- Use WinSCP to connect to Controller via SSH - Use SCP type connection
Controller user and Pass (Use above instructions to log into 3.1.1/.2)
Username: root
Password: t0talc0ntr0l4!
Username: root
Password: t0talc0ntr0l4!
- Go to /etc/openvpn and Copy or Backup clientca-prod.pem to your desktop. Copy 'Director Patch' version of clientca-prod.pem onto controller if using 2.10 or earlier. Reboot the Controller. You can also use the System Manager to disable Director and Broker services and then reenable them. This should also work but a reboot will always work.
- This previous step will get your controller up and running but you will need to merge the certs from the controller and the Director Patch clientca-prod.pem (2.10 or earlier) or ca_cert.pem certs (3.0 or later). See 5b or 5c below.
Previous steps for all versions of Composer/Controller software up to 3.0
5b. You should concatenate the two clientca-prod.pem files from your Controller and the Director Patch. Using the two clientca-prod.pem files mentioned above (one from the Controller and one from the Director Patch), open the one from the Controller and go to the end of the file. Add 'Director Patch' clientca-prod.pem certs. You now have a 'good' cert file. WinSCP back into the Controller and upload this new clientca-prod.pem file to /etc/openvpn. Reboot the Controller.
5b. You should concatenate the two clientca-prod.pem files from your Controller and the Director Patch. Using the two clientca-prod.pem files mentioned above (one from the Controller and one from the Director Patch), open the one from the Controller and go to the end of the file. Add 'Director Patch' clientca-prod.pem certs. You now have a 'good' cert file. WinSCP back into the Controller and upload this new clientca-prod.pem file to /etc/openvpn. Reboot the Controller.
New steps for Composer/Controller software 3.0 and above - These should work for versions 2.10 but are confirmed for 3.0 and up.
5c. For Composer 3.x, you should concatenate the clientca-prod.pem file from your Controller and the cert from the ca_cert.pem file to the end. To do this, open the clientca-prod.pem file you downloaded from your Controller and go to the end of the file. Add the ca_cert.pem cert. You now have a 'good' cert file. WinSCP back into the Controller and upload this new clientca-prod.pem file to /etc/openvpn. Reboot the Controller.
5c. For Composer 3.x, you should concatenate the clientca-prod.pem file from your Controller and the cert from the ca_cert.pem file to the end. To do this, open the clientca-prod.pem file you downloaded from your Controller and go to the end of the file. Add the ca_cert.pem cert. You now have a 'good' cert file. WinSCP back into the Controller and upload this new clientca-prod.pem file to /etc/openvpn. Reboot the Controller.
6. Now install the version of Composer you want to use (2.10.x, 3.1.1/.2) and edit the following. Make a backup of composerPro.exe.config in the Control4/Controller directory and then edit the original with Notepad.
Under Web change:
key='LicensingURL' value='false'
key='DealerAccountLocatorURL' value='false'
Under Web change:
key='LicensingURL' value='false'
key='DealerAccountLocatorURL' value='false'
For 3.1.3 - Different edit
Change from 'string' to '0' (zero) this line
'ComposerPro_LicensingService_Licensing' serializeAs='0'
Change from 'string' to '0' (zero) this line
'ComposerPro_LicensingService_Licensing' serializeAs='0'
7. Start the new composer and upgrade your controller. After this you will have to patch the director/controller again using the above WinSCP method.
8. *If you need to register your controller for first time use, use these additional instructions:
To register a controller first build a project and add a controller in Composer. Then link the controller under with the IP/SDDP address in connections. After that go back and register the controller under Tools -> Account Settings. Exit Composer.
9. That should be everything to get you up and running
If you see the Json error:
**************For the Json issues:
Replace Composer 2.5.3 Composer.exe with the 'Special Exe' one (the one that causes the ca_cert.srl, composer.p12 and openssl.conf files to be created. - Re-copy the special composer to 2.5.3 and re-run steps above to complete the email and pass. This will create the composer.p12.
***********************
Another step(s) if using older version:
0. If running a controller older than 2.10.2 run the C4_Cert_Replacement_Patch to update the certs on it to the latest ones. This should also fix controller 'check in' issues if you had them.
6. Copy over the Director Patch clientca-prod.pem so your controller has the correct cert as if you had it patched before step 0 overwrote it.
**Updated 6/3/20 to include 3.1.3 (only one change from below instructions)
**Updated 1/26/20 to include 3.1.1/.2 install and changes
**The guide now has a section broken out for the 1 Yr Cert Renewal and another for controller registration
**The guide now has a section broken out for the 1 Yr Cert Renewal and another for controller registration
Common commands and information.
Default Controller User and Pass:
Username: root
Password: t0talc0ntr0l4!
(3.1.1/.2+ NOTE - Once Composer connects to the controller, the password will automatically be changed. Details below.)
Default Controller User and Pass:
Username: root
Password: t0talc0ntr0l4!
(3.1.1/.2+ NOTE - Once Composer connects to the controller, the password will automatically be changed. Details below.)
Commands to add root user and password:
Command to add new user: adduser USER
Command to change password: passwd
Composer 3.1.1/.2+ is slightly different than previous versions. - Run Composer and when the Controller selection box comes up, right click on the controller and it will bring up a box to start a Terminal session. You need to change the root password so that you can SCP the clientca-prod.pem file to the controller. Type 'passwd' then enter a new password. You now have root access with a password. **NOTE: After you connect to your controller via Composer 3.1.1/.2+, the root password will be removed so this step must happen any time you need to SCP to the controller to update the clientca-prod.pem certs. Or, set up a new user with root access. Details below.
Command to add new user: adduser USER
Command to change password: passwd
Composer 3.1.1/.2+ is slightly different than previous versions. - Run Composer and when the Controller selection box comes up, right click on the controller and it will bring up a box to start a Terminal session. You need to change the root password so that you can SCP the clientca-prod.pem file to the controller. Type 'passwd' then enter a new password. You now have root access with a password. **NOTE: After you connect to your controller via Composer 3.1.1/.2+, the root password will be removed so this step must happen any time you need to SCP to the controller to update the clientca-prod.pem certs. Or, set up a new user with root access. Details below.
Adding permanent root user access:
Type adduser USER with USER being the name of the user you are creating. Enter your chosen password. Verify it.
Normally you could use the usermod command but it isn't available. So edit /etc/passwd
Look for the line with the user name you just created.
user:$kdlskfj.$dklj.$jklj/:XXX:XXX:Linux User,blahblahblah. Change whatever number is in both XXX spots to 0:0.
user:$kdlskfj.$dklj.$jklj/:0:0:Linux User,blahblahblah
Save the file. Reboot.
You now have a new user with root access
Type adduser USER with USER being the name of the user you are creating. Enter your chosen password. Verify it.
Normally you could use the usermod command but it isn't available. So edit /etc/passwd
Look for the line with the user name you just created.
user:$kdlskfj.$dklj.$jklj/:XXX:XXX:Linux User,blahblahblah. Change whatever number is in both XXX spots to 0:0.
user:$kdlskfj.$dklj.$jklj/:0:0:Linux User,blahblahblah
Save the file. Reboot.
You now have a new user with root access
Hey guys, I just threw this together so it would be great if you can provide comments or information to make sure it's correct. I've placed the correct files in the download.
Definitive Install Guide
Items Needed:
Composer 2.5.3
Composer 2.5.3 Composer.exe (cracked) 'Special Exe'
Certs (ca.pem and ca_cert.pem)
Composer 3.1.x (Composer 3.1.1/.2/.3 has some slightly different instructions)
MeeKah Composer Patch (No longer needed in 3.1.x)
Director Patch (Just the clientca-prod.pem certs which have been extracted in the below zip file) (No longer needed in 3.1.x)
C4_Cert_Replacement_Patch
C4_Device_Image_Updater_V2
WinSCP
Composer 2.5.3
Composer 2.5.3 Composer.exe (cracked) 'Special Exe'
Certs (ca.pem and ca_cert.pem)
Composer 3.1.x (Composer 3.1.1/.2/.3 has some slightly different instructions)
MeeKah Composer Patch (No longer needed in 3.1.x)
Director Patch (Just the clientca-prod.pem certs which have been extracted in the below zip file) (No longer needed in 3.1.x)
C4_Cert_Replacement_Patch
C4_Device_Image_Updater_V2
WinSCP
If someone can upload or link the files above, that would be great.
A Helpful link:
For a quick way to search for Drivers without going into Composer you can go here:
http://drivers.control4.com/solr/drivers/browse?q=
For a quick way to search for Drivers without going into Composer you can go here:
http://drivers.control4.com/solr/drivers/browse?q=
All User Manuals are now accessible through Composer 3.1.x
****UPDATED TO BRING 1 YR CERT RENEWAL TO ITS OWN SECTION****
1.Make sure you have Composer 2.5.3 installed.
2.Rename 2.5.3 Composer.exe to a backup (Composer Bak.exe) then copy the 'Special Exe' Composer.exe into the directory. Run Special Composer.exe. Fill in email and password. Click OK.
2.Rename 2.5.3 Composer.exe to a backup (Composer Bak.exe) then copy the 'Special Exe' Composer.exe into the directory. Run Special Composer.exe. Fill in email and password. Click OK.
If email and password form doesn't come up when you start Composer, delete composer.p12 from the AppDataRoamingControl4Composer folder and re-run or re-copy over the Composer 2.5.3 Composer.exe (cracked) 'Special Exe'. Run Composer.exe. It should come up at this point and is needed to update one of the cert files. Verify that (ca_cert.srl, composer.p12 and openssl.conf) files have been created and updated. composer.p12 is the file which needs to be generated every year and this is how you update it.
*****Register Controller****
You can register your controller in 3.x with a couple of ComposerPro.exe.config changes. These may also work in 2.10 but I never tested.
Changing ComposerPro.exe.config (3.1.1/.2/NOT .3):
Under Web change:
key='LicensingURL' value='false'
key='DealerAccountLocatorURL' value='false'
Under Web change:
key='LicensingURL' value='false'
key='DealerAccountLocatorURL' value='false'
Changing ComposerPro.exe.config (3.1.3):
Change from 'string' to '0' (zero) this line
'ComposerPro_LicensingService_Licensing' serializeAs='0'
Change from 'string' to '0' (zero) this line
'ComposerPro_LicensingService_Licensing' serializeAs='0'
This change allows you access to Account Services, where you can register your controller, and bypasses the initial login dialog. By changing this config, there is also no need for MeeKah Patch.
***Install Guide****
Starting out, and for hygiene, do the following:
- Uninstall all versions of ComposerPro/HE/etc.
- Remove Control4 Directory in - Program Files (x86)Control4 or C:Program FilesControl4
- Remove Control4 Directory in - UsersxxxxAppDataRoamingControl4
- Uninstall all versions of ComposerPro/HE/etc.
- Remove Control4 Directory in - Program Files (x86)Control4 or C:Program FilesControl4
- Remove Control4 Directory in - UsersxxxxAppDataRoamingControl4
That should be all you need to 'start fresh'.
1. Install Composer 2.5.3 (Do not run yet.)
2. Copy Cert files ca.pem and ca_cert.pem to AppDataRoamingControl4Composer folder
3. Go to 'Program Files (x86)Control4Composer253' Rename 2.5.3 Composer.exe to a backup (Composer Bak.exe) then copy the 'Special Exe' Composer.exe into the directory. This special Composer.exe will be the one that causes the ca_cert.srl, composer.p12 and openssl.conf files to be created.
4. Run the Special Composer.exe and you will be presented with a login dialog box. Type in an email and password (it doesn't matter what they are) and submit. (You should check to make sure the files, I mentioned above, show up in the AppDataRoamingControl4Composer folder). If the composer.p12 file is not created, recopy the Special Exe and rerun.
5. **Edit - The Director Patch isn't used any longer, so please use the following steps instead. They always work. If you are using 2.10 or earlier use the Director Patch clientca-prod.pem (Step 5b). The cert you need, clientca-prod.pem, is already extracted and located in the download of this post. If you are using 3.x use the ca_cert.pem certs (Step 5c).
***Use WinSCP to copy over clientca-prod.pem to your controller.
***Use WinSCP to copy over clientca-prod.pem to your controller.
Open Director Patch Folder
5a. WinSCP into the Controller (Director)
- Use WinSCP to connect to Controller via SSH - Use SCP type connection
- Use WinSCP to connect to Controller via SSH - Use SCP type connection
Controller user and Pass (Use above instructions to log into 3.1.1/.2)
Username: root
Password: t0talc0ntr0l4!
Username: root
Password: t0talc0ntr0l4!
- Go to /etc/openvpn and Copy or Backup clientca-prod.pem to your desktop. Copy 'Director Patch' version of clientca-prod.pem onto controller if using 2.10 or earlier. Reboot the Controller. You can also use the System Manager to disable Director and Broker services and then reenable them. This should also work but a reboot will always work.
- This previous step will get your controller up and running but you will need to merge the certs from the controller and the Director Patch clientca-prod.pem (2.10 or earlier) or ca_cert.pem certs (3.0 or later). See 5b or 5c below.
Previous steps for all versions of Composer/Controller software up to 3.0
5b. You should concatenate the two clientca-prod.pem files from your Controller and the Director Patch. Using the two clientca-prod.pem files mentioned above (one from the Controller and one from the Director Patch), open the one from the Controller and go to the end of the file. Add 'Director Patch' clientca-prod.pem certs. You now have a 'good' cert file. WinSCP back into the Controller and upload this new clientca-prod.pem file to /etc/openvpn. Reboot the Controller.
5b. You should concatenate the two clientca-prod.pem files from your Controller and the Director Patch. Using the two clientca-prod.pem files mentioned above (one from the Controller and one from the Director Patch), open the one from the Controller and go to the end of the file. Add 'Director Patch' clientca-prod.pem certs. You now have a 'good' cert file. WinSCP back into the Controller and upload this new clientca-prod.pem file to /etc/openvpn. Reboot the Controller.
New steps for Composer/Controller software 3.0 and above - These should work for versions 2.10 but are confirmed for 3.0 and up.
5c. For Composer 3.x, you should concatenate the clientca-prod.pem file from your Controller and the cert from the ca_cert.pem file to the end. To do this, open the clientca-prod.pem file you downloaded from your Controller and go to the end of the file. Add the ca_cert.pem cert. You now have a 'good' cert file. WinSCP back into the Controller and upload this new clientca-prod.pem file to /etc/openvpn. Reboot the Controller.
5c. For Composer 3.x, you should concatenate the clientca-prod.pem file from your Controller and the cert from the ca_cert.pem file to the end. To do this, open the clientca-prod.pem file you downloaded from your Controller and go to the end of the file. Add the ca_cert.pem cert. You now have a 'good' cert file. WinSCP back into the Controller and upload this new clientca-prod.pem file to /etc/openvpn. Reboot the Controller.
6. Now install the version of Composer you want to use (2.10.x, 3.1.1/.2) and edit the following. Make a backup of composerPro.exe.config in the Control4/Controller directory and then edit the original with Notepad.
Under Web change:
key='LicensingURL' value='false'
key='DealerAccountLocatorURL' value='false'
Under Web change:
key='LicensingURL' value='false'
key='DealerAccountLocatorURL' value='false'
For 3.1.3 - Different edit
Change from 'string' to '0' (zero) this line
'ComposerPro_LicensingService_Licensing' serializeAs='0'
Change from 'string' to '0' (zero) this line
'ComposerPro_LicensingService_Licensing' serializeAs='0'
7. Start the new composer and upgrade your controller. After this you will have to patch the director/controller again using the above WinSCP method.
8. *If you need to register your controller for first time use, use these additional instructions:
To register a controller first build a project and add a controller in Composer. Then link the controller under with the IP/SDDP address in connections. After that go back and register the controller under Tools -> Account Settings. Exit Composer.
9. That should be everything to get you up and running
If you see the Json error:
**************For the Json issues:
Replace Composer 2.5.3 Composer.exe with the 'Special Exe' one (the one that causes the ca_cert.srl, composer.p12 and openssl.conf files to be created. - Re-copy the special composer to 2.5.3 and re-run steps above to complete the email and pass. This will create the composer.p12.
***********************
Another step(s) if using older version:
0. If running a controller older than 2.10.2 run the C4_Cert_Replacement_Patch to update the certs on it to the latest ones. This should also fix controller 'check in' issues if you had them.
6. Copy over the Director Patch clientca-prod.pem so your controller has the correct cert as if you had it patched before step 0 overwrote it.
Uploaded files:This is awesome - thanks for posting!
This is awesome - thanks for posting!
I'm behind the times on all this, having moved and not brought (much) Control4 with me. However, I can 'sticky' this post now or wait to see if there's any further feedback..?
I'm behind the times on all this, having moved and not brought (much) Control4 with me. However, I can 'sticky' this post now or wait to see if there's any further feedback..?
Thanks,
I've compiled all this information through reading and trial and error and most of the questions involving upgrades and certs etc is all contained here. If you could sticky, I believe it will be worth while. Thanks.
Renamed the title to better reflect what it's about.
Thanks,
I've compiled all this information through reading and trial and error and most of the questions involving upgrades and certs etc is all contained here. If you could sticky, I believe it will be worth while. Thanks.
Renamed the title to better reflect what it's about.
Thank you! This is exactly what I was looking for, an up to date guide.
I want to add some things that I learned. If you have an older hc250 system, perhaps you purchased it from ebay:
1. Start by doing a factory reset. You may end up on firmware 2.5.3 but you may end up on an older one.
2. Either way, you must do the C4_Cert_Replacement_Patch first before you do anything else.
3. After the patch, then add the clientca-prod.pem entries.
4. That will allow you to both connect with the patched Composer 2.5.3 and to register the unit. To register, simply create a control4 account, choose a random dealer when asked, and then get your registration code. Connect with the patched Composer 2.5.3, select Account Services from the upper menu bar. Put in your registration code, and you should be set. If you get an SSL error, you probably didn't do the C4_Cert_Replacement_Patch, or you may have accidentally wiped the patch by doing a factory reset/install.
5. Once you are registered, you can update to any version you want using either the composer update tool or the control4 image updater tool. After any install, you must do the clientca-prod.pem to connect again with Composer. If you get an ssl error while trying an update, you again may need to do the C4_Cert_Replacement_Patch.
I hope that helps. I spent hours figuring this stuff out.
Thank you! This is exactly what I was looking for, an up to date guide.
I want to add some things that I learned. If you have an older hc250 system, perhaps you purchased it from ebay:
1. Start by doing a factory reset. You may end up on firmware 2.5.3 but you may end up on an older one.
2. Either way, you must do the C4_Cert_Replacement_Patch first before you do anything else.
3. After the patch, then add the clientca-prod.pem entries.
4. That will allow you to both connect with the patched Composer 2.5.3 and to register the unit. To register, simply create a control4 account, choose a random dealer when asked, and then get your registration code. Connect with the patched Composer 2.5.3, select Account Services from the upper menu bar. Put in your registration code, and you should be set. If you get an SSL error, you probably didn't do the C4_Cert_Replacement_Patch, or you may have accidentally wiped the patch by doing a factory reset/install.
5. Once you are registered, you can update to any version you want using either the composer update tool or the control4 image updater tool. After any install, you must do the clientca-prod.pem to connect again with Composer. If you get an ssl error while trying an update, you again may need to do the C4_Cert_Replacement_Patch.
I hope that helps. I spent hours figuring this stuff out.
Thanks Mark55,
Your instructions are better than my 'Additional Instructions Step 0)' above.
I wanted to pass along some additional info that I found out this weekend. I did a factory reset on my EA1, somewhat unintentionally.
I wanted to pass along some additional info that I found out this weekend. I did a factory reset on my EA1, somewhat unintentionally.
The C4_Cert_Replacement_Patch is important because it contains RSA certs that allow it to authenticate with the Control4 servers. So, ALL versions of Control4 Directors will need to be running with this cert or you won't be able to register or update your system.
One big issue I ran into was that I forgot to back up my config after I had upgraded to 3.0 the first time. When I did a factory reset, my director was downgraded to 2.9. When I upgraded, using the steps above, including the C4_Cert_Replacement_Patch, I was unable to load my 2.10 config into Composer 3.0 because Control4 Composer removed some of the Agents (4Store, others.). You would think that the Composer software would be smart enough to let you remove the Agent when trying to load it. It won't. I had to downgrade to 2.10 (Using the C4_Device_Image_Updater), load the config, remove the Agents, then upgrade back to 3.0. After that, everything went well. I wish I would have backed up the config first as it would have saved many, many steps.
Thanks Mark55,
Your instructions are better than my 'Additional Instructions Step 0)' above.
I wanted to pass along some additional info that I found out this weekend. I did a factory reset on my EA1, somewhat unintentionally.
I wanted to pass along some additional info that I found out this weekend. I did a factory reset on my EA1, somewhat unintentionally.
The C4_Cert_Replacement_Patch is important because it contains RSA certs that allow it to authenticate with the Control4 servers. So, ALL versions of Control4 Directors will need to be running with this cert or you won't be able to register or update your system.
One big issue I ran into was that I forgot to back up my config after I had upgraded to 3.0 the first time. When I did a factory reset, my director was downgraded to 2.9. When I upgraded, using the steps above, including the C4_Cert_Replacement_Patch, I was unable to load my 2.10 config into Composer 3.0 because Control4 Composer removed some of the Agents (4Store, others.). You would think that the Composer software would be smart enough to let you remove the Agent when trying to load it. It won't. I had to downgrade to 2.10 (Using the C4_Device_Image_Updater), load the config, remove the Agents, then upgrade back to 3.0. After that, everything went well. I wish I would have backed up the config first as it would have saved many, many steps.
Multimarkdown Composer 4 Pro 4 5 12 Volt
Have the certs changed in the last year?
Last time I made a change to my project was almost a year ago on 09/10/2018
A coupe of weeks ago I started having issues with controlling some devices other than lights with Alexa.
Eventually realized my 4sight had recently expired so activated again. Even after this I still had issues with turning on other devices.
This morning I tried to connecting from Composer 2.10.2 using exactly the same setup I had previously except for a Windows update (I use a VM) and now I get an error 'Exception: Error reading JToken from JsonReader.Path ', line 0, postition 0.'.
Reading other thread based on this error I should be able to open Compose 2.5.3
'In case anyone goes through the whole process. Make sure to keep 2.5.3 installed. Microsoft edge 79 0 309 15 epizoda. About a month after installing 2.9.0 I got the broker not connected error. I tried just about everything and couldn’t get it fixed. I realized that anything under 2.8 would allow me to login but since it’s old I could not make changes… this let me to try other versions. When I opened 2.5.3 it asked me for my control4 login. After entering it I was able to use 2.9 composer so it looks like it updates the certificates. This will save a lot of hassle the next time the certificates expire.'
However when I open 2.5.3 it doesn't prompt for a user ID or password. I did not login to my controller.
Thanks,
[EDIT]
I checked my /etc/openvpn directory and noticed that client.pem and client.key files where updated, so I copied the files had had from a year ago (I had backups).
I then disable director, disabled broker, enabled director, enabled broker and still have the connection problem
Have the certs changed in the last year?
Last time I made a change to my project was almost a year ago on 09/10/2018
A coupe of weeks ago I started having issues with controlling some devices other than lights with Alexa.
Eventually realized my 4sight had recently expired so activated again. Even after this I still had issues with turning on other devices.
This morning I tried to connecting from Composer 2.10.2 using exactly the same setup I had previously except for a Windows update (I use a VM) and now I get an error 'Exception: Error reading JToken from JsonReader.Path ', line 0, postition 0.'.
Reading other thread based on this error I should be able to open Compose 2.5.3
'In case anyone goes through the whole process. Make sure to keep 2.5.3 installed. About a month after installing 2.9.0 I got the broker not connected error. I tried just about everything and couldn’t get it fixed. I realized that anything under 2.8 would allow me to login but since it’s old I could not make changes… this let me to try other versions. When I opened 2.5.3 it asked me for my control4 login. After entering it I was able to use 2.9 composer so it looks like it updates the certificates. This will save a lot of hassle the next time the certificates expire.'
However when I open 2.5.3 it doesn't prompt for a user ID or password. I did not login to my controller.
Thanks,
[EDIT]
I checked my /etc/openvpn directory and noticed that client.pem and client.key files where updated, so I copied the files had had from a year ago (I had backups).
I then disable director, disabled broker, enabled director, enabled broker and still have the connection problem
emont69,
If you go back and read post #1 you will see a note about the JSON issue you are encountering. It is at the end of the guide. You are getting the JSON notice because composer.p12 hasn't been created or has expired. It sounds like you have used the MeeKah Patch on 2.5.3, since you aren't getting the email and password login screen any longer. You need to replace the 2.5.3 composer.exe file with the 'special 2.5.3 composer.exe' file and then connect to your controller. Again, make sure composer.p12 gets created and you will be good to connect with any version of Composer after applying the Meekah Patch.
If you go back and read post #1 you will see a note about the JSON issue you are encountering. It is at the end of the guide. You are getting the JSON notice because composer.p12 hasn't been created or has expired. It sounds like you have used the MeeKah Patch on 2.5.3, since you aren't getting the email and password login screen any longer. You need to replace the 2.5.3 composer.exe file with the 'special 2.5.3 composer.exe' file and then connect to your controller. Again, make sure composer.p12 gets created and you will be good to connect with any version of Composer after applying the Meekah Patch.
Multimarkdown Composer 4 Pro 4 5 12 Amp
You will have to use 2.5.3 with the special composer.exe to regenerate the composer.p12 file every year. So, don't remove 2.5.3, you will need it, and don't Meekah patch it, there is no need.
I hope that gets you up and running. It should resolve your issues.
emont69,
If you go back and read post #1 you will see a note about the JSON issue you are encountering. It is at the end of the guide. You are getting the JSON notice because composer.p12 hasn't been created or has expired. It sounds like you have used the MeeKah Patch on 2.5.3, since you aren't getting the email and password login screen any longer. You need to replace the 2.5.3 composer.exe file with the 'special 2.5.3 composer.exe' file and then connect to your controller. Again, make sure composer.p12 gets created and you will be good to connect with any version of Composer after applying the Meekah Patch.
If you go back and read post #1 you will see a note about the JSON issue you are encountering. It is at the end of the guide. You are getting the JSON notice because composer.p12 hasn't been created or has expired. It sounds like you have used the MeeKah Patch on 2.5.3, since you aren't getting the email and password login screen any longer. You need to replace the 2.5.3 composer.exe file with the 'special 2.5.3 composer.exe' file and then connect to your controller. Again, make sure composer.p12 gets created and you will be good to connect with any version of Composer after applying the Meekah Patch.
You will have to use 2.5.3 with the special composer.exe to regenerate the composer.p12 file every year. So, don't remove 2.5.3, you will need it, and don't Meekah patch it, there is no need.
I hope that gets you up and running. It should resolve your issues.
Quote from emont69 on August 31, 2019, 11:34 am
Have the certs changed in the last year?
[EDIT]
I checked my /etc/openvpn directory and noticed that client.pem and client.key files where updated, so I copied the files had had from a year ago (I had backups).
I then disable director, disabled broker, enabled director, enabled broker and still have the connection problem
emont- I went through this last night in a different fashion after my 4sight stopped working. My composerPro still worked on 2.10.6 but i was trying to upgrade to 3.0 as I acquired new touch screens. The update ran fine but then my issues compounded outside of 4Sight.
Multimarkdown Composer 4 Pro 4 5 12 Battery
I did a few things. 1. SCP the clientca_prod.pem to the director and restarted. 2. Opened up 2.5.3 special exe via Run as Administrator, which did get me the prompt to login. however I will note that the last time I had to login to control4 site and unregister my controller first and then re-register. 3. Clicked through dozens of warning prompts and closed 2.5.3 special exe. 4. Ran composerpro just fine
Multimarkdown Composer 4 Pro 4 5 12 Days Of
This is assuming you had a working setup after the May 2018 certificate patching. If you did not then you likely need to reinstall your composer setup, the process to update otherwise is a tad cumbersome and prone to a cyclical process.
Have the certs changed in the last year?
[EDIT]
I checked my /etc/openvpn directory and noticed that client.pem and client.key files where updated, so I copied the files had had from a year ago (I had backups).
I then disable director, disabled broker, enabled director, enabled broker and still have the connection problem
emont- I went through this last night in a different fashion after my 4sight stopped working. My composerPro still worked on 2.10.6 but i was trying to upgrade to 3.0 as I acquired new touch screens. The update ran fine but then my issues compounded outside of 4Sight.
I did a few things. 1. SCP the clientca_prod.pem to the director and restarted. 2. Opened up 2.5.3 special exe via Run as Administrator, which did get me the prompt to login. however I will note that the last time I had to login to control4 site and unregister my controller first and then re-register. 3. Clicked through dozens of warning prompts and closed 2.5.3 special exe. 4. Ran composerpro just fine
This is assuming you had a working setup after the May 2018 certificate patching. If you did not then you likely need to reinstall your composer setup, the process to update otherwise is a tad cumbersome and prone to a cyclical process.
Thanks for the help I got it to work with the following
Uninstall Composer 2.5.3
Multimarkdown Composer 4 Pro 4 5 12 And 33 42
Cleaning the UsersxxxxAppDataRoamingControl4Composer directory
1. Install Composer 2.5.3 (Do not run yet!)
2. Copy Cert files ca.pem and ca_cert.pem to UsersxxxxAppDataRoamingControl4Composer folder
3. Go to 'Program Files (x86)Control4Composer253' Rename 2.5.3 Composer.exe to a backup (Composer Bak.exe) then copy the 'special exe' Composer.exe into the directory.
4. Run the new Composer.exe and type in any email and password and submit.
5. Run the Director Patch
Thanks for the help I got it to work with the following
Uninstall Composer 2.5.3
Cleaning the UsersxxxxAppDataRoamingControl4Composer directory
1. Install Composer 2.5.3 (Do not run yet!)
2. Copy Cert files ca.pem and ca_cert.pem to UsersxxxxAppDataRoamingControl4Composer folder
3. Go to 'Program Files (x86)Control4Composer253' Rename 2.5.3 Composer.exe to a backup (Composer Bak.exe) then copy the 'special exe' Composer.exe into the directory.
4. Run the new Composer.exe and type in any email and password and submit.
Multimarkdown Composer 4 Pro 4 5 12 Commentary
5. Run the Director Patch