Request Tracker Wiki - User contributions [en]

Main Page

2019-02-15T01:15:29Z

Mis: /* Common problems */ Certbot is from EFF not LetsEncrypt

== RT ==

RT is an open source issue tracking and workflow platform developed and supported by [https://bestpractical.com Best Practical Solutions]. This wiki site is a free resource for the RT community to share ideas, configurations, and customizations to RT, RTIR, and related products.

Please: [[UpdateTheWiki]], post your hints, tricks, tips and tools about how to get the most out of RT. If you currently use RT, please head over to [[RTUsers]] and add yourself and your organization to the user list.

== Wiki Move ==

We've recently migrated the RT wiki and all of its content from an instance hosted by Wikia to this instance. If you had a user account on the previous wiki, you'll need to [[Special:UserLogin|create your account again]]. However, all of your content has been migrated over. If you were a contributor on the previous wiki and you see things are out of place, please feel free to rearrange things and fix them up.

We're tracking details from the move on the [[Wikia Move]] page.

== Other Documentation ==

In addition to the information found here, you can find more RT's documentation in your install of RT on the server and also [https://bestpractical.com/resources/ on the web at the Best Practical website]. The [https://bestpractical.com/blog Best Practical blog] is another great resource for RT information.

== Sections ==

You can go through these pretty much in order if you're starting from scratch, but please plan to spend some quality time with the [[UserManual]] before you try to go live; RT is big and full of tons of features, and you probably can't get your head around all of it in one sitting.

* [[FAQ]], [[FindingAnswersAboutRT]] and "Common Problems" below.
* [[BugReporting]]
* [[HowToHelp]], [[Translation]]
* [[Demo]]
* [[UserManual]], [[RTGlossary]] & [[Documentation]]
* [[InstallationGuides]], [[RTTutorials]]
* [[RT Config|RT_Config]] & [[RT SiteConfig|RT_SiteConfig]]

* [[Extensions]] to RT available as installable plugins
* [[Contributions]] by the community to customize RT
* [[RTIR]] RT for Incident Response
* [[RTFM]] RT FAQ Manager

* [[RTHistory]]
* [[InThePress]]
* [[REST]] API
* Customizing with [[CustomizingWithCallbacks|Callbacks]]

=== Common problems ===

* [[CantLocateObject]] - Can't locate object method "new" via package "<code>RT::Handle</code>" at rt3/lib/RT.pm
* [[NoConnectionToSyslog]] - no connection to syslog
* [[NoRecipFound]] - No recipients found. Not sending
* Getting information out of RT3 for [[reporting]] or inclusion elsewhere.
* [[PermissionDenied]] emails|
* Getting RT4.x to play nice with [[certbot]] to obtain free SSL certificates from [http://letsencrypt.org LetsEncrypt].

== Wish lists ==

* [[WikiWishList]] - wish list for this wiki
* [[WishList]] - wish list for the RT
* [[RT3StatisticsPackageWishList]]

== Getting started with MediaWiki ==

To learn more about how to edit wiki pages, click the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents Help] link here or in the navigation on the left.

We have installed the Markdown plugin, so you can edit pages in Markdown.

Certbot

2019-02-15T01:12:32Z

Mis: Certbot is by eff not by letsencrypt

=== Returning content NOT in RT such as ACME challenges for certbot ===

Getting RT to serve static content can seem to be quite an issue, especially if it is to be dynamically created such as the ACME challenge/response that [https://certbot.eff.org certbot] uses to get [http://letsencrypt.org LetsEncrypt] free SSL certificates. The solution is quite simple. In your RT_SiteConfig.pm you can add the StaticRoots directive to serve static pages. Follows is an example of how to use this feature for obtaining [https://certbot.eff.org certbot] authorised requests:
<nowiki>
Set( @StaticRoots,
{
path => sub { s!^/.well-known/!! },
root => '/usr/local/share/html/.well-known/'
},
);</nowiki>

After restarting your RT server, you can then issue a certbot request as follows:
<nowiki>
certbot certonly --webroot -w /usr/local/share/html -d <your domain or rt hostname></nowiki>

'''Note:''' This assumes '/usr/local/share/html' is your document root, change as appropriate to your site, it does '''not''' have to be the location of your RT server or files.

You can then install the certificate in your webserver as per it's documentation, by default the keys and certificates will be located in:
<nowiki>
/etc/letsencrypt/live/<your domain or rt hostname>/cert.pem
/etc/letsencrypt/live/<your domain or rt hostname>/fullchain.pem
/etc/letsencrypt/live/<your domain or rt hostname>/privkey.pem</nowiki>
To finish the installation and make certificate renewals automatic on UNIX you can add the following to crontab:
<nowiki>
2 2 1 * * /usr/local/bin/certbot renew --webroot -w /usr/local/share/html -d <your domain or rt hostname> && service apache24 restart</nowiki>

Certbot

2019-02-15T01:10:20Z

Mis: Added links to certbot

=== Returning content NOT in RT such as ACME challenges for certbot ===

Getting RT to serve static content can seem to be quite an issue, especially if it is to be dynamically created such as the ACME challenge/response that [http://letsencrypt.org LetsEncrypt's] [https://certbot.eff.org certbot] uses. The solution is quite simple. In your RT_SiteConfig.pm you can add the StaticRoots directive to serve static pages. Follows is an example of how to use this feature for obtaining [https://certbot.eff.org certbot] authorised requests:
<nowiki>
Set( @StaticRoots,
{
path => sub { s!^/.well-known/!! },
root => '/usr/local/share/html/.well-known/'
},
);</nowiki>

After restarting your RT server, you can then issue a certbot request as follows:
<nowiki>
certbot certonly --webroot -w /usr/local/share/html -d <your domain or rt hostname></nowiki>

'''Note:''' This assumes '/usr/local/share/html' is your document root, change as appropriate to your site, it does '''not''' have to be the location of your RT server or files.

You can then install the certificate in your webserver as per it's documentation, by default the keys and certificates will be located in:
<nowiki>
/etc/letsencrypt/live/<your domain or rt hostname>/cert.pem
/etc/letsencrypt/live/<your domain or rt hostname>/fullchain.pem
/etc/letsencrypt/live/<your domain or rt hostname>/privkey.pem</nowiki>
To finish the installation and make certificate renewals automatic on UNIX you can add the following to crontab:
<nowiki>
2 2 1 * * /usr/local/bin/certbot renew --webroot -w /usr/local/share/html -d <your domain or rt hostname> && service apache24 restart</nowiki>

Certbot

2019-02-15T01:04:33Z

Mis:

=== Returning content NOT in RT such as ACME challenges for certbot ===

Getting RT to serve static content can seem to be quite an issue, especially if it is to be dynamically created such as the ACME challenge/response that [http://letsencrypt.org LetsEncrypt's] certbot uses. The solution is quite simple. In your RT_SiteConfig.pm you can add the StaticRoots directive to serve static pages. Follows is an example of how to use this feature for obtaining certbot authorised requests:
<nowiki>
Set( @StaticRoots,
{
path => sub { s!^/.well-known/!! },
root => '/usr/local/share/html/.well-known/'
},
);</nowiki>

After restarting your RT server, you can then issue a certbot request as follows:
<nowiki>
certbot certonly --webroot -w /usr/local/share/html -d <your domain or rt hostname></nowiki>

'''Note:''' This assumes '/usr/local/share/html' is your document root, change as appropriate to your site, it does '''not''' have to be the location of your RT server or files.

You can then install the certificate in your webserver as per it's documentation, by default the keys and certificates will be located in:
<nowiki>
/etc/letsencrypt/live/<your domain or rt hostname>/cert.pem
/etc/letsencrypt/live/<your domain or rt hostname>/fullchain.pem
/etc/letsencrypt/live/<your domain or rt hostname>/privkey.pem</nowiki>
To finish the installation and make certificate renewals automatic on UNIX you can add the following to crontab:
<nowiki>
2 2 1 * * /usr/local/bin/certbot renew --webroot -w /usr/local/share/html -d <your domain or rt hostname> && service apache24 restart</nowiki>

Certbot

2019-02-15T00:59:59Z

Mis:

=== Returning content NOT in RT such as ACME challenges for certbot ===

Getting RT to serve static content can seem to be quite an issue, especially if it is to be dynamically created such as the ACME challenge/response that [http://letsencrypt.org LetsEncrypt's] certbot uses. The solution is quite simple. In your RT_SiteConfig.pm you can add the StaticRoots directive to serve static pages. Follows is an example of how to use this feature for obtaining certbot authorised requests:
<nowiki>
Set( @StaticRoots,
{
path => sub { s!^/.well-known/!! },
root => '/usr/local/share/html/.well-known/'
},
);</nowiki>

After restarting your RT server, you can then issue a certbot request as follows:
<nowiki>
certbot certonly --webroot -w /usr/local/share/html -d <your domain or rt hostname></nowiki>

'''Note:''' This assumes '/usr/local/share/html' is your document root, change as appropriate to your site, it does '''not''' have to be the location of your RT server or files.

You can then install the certificate in your webserver as per it's documentation, by default the keys and certificates will be located in:
<nowiki>
/etc/letsencrypt/live/<your domain or rt hostname>/fullchain.pem
/etc/letsencrypt/live/<your domain or rt hostname>/privkey.pem</nowiki>
To finish the installation and make certificate renewals automatic on UNIX you can add the following to crontab:
<nowiki>
2 2 1 * * /usr/local/bin/certbot renew --webroot -w /usr/local/share/html -d <your domain or rt hostname> && service apache24 restart</nowiki>

Certbot

2019-02-15T00:59:24Z

Mis: Added auto-renew text

=== Returning content NOT in RT such as ACME challenges for certbot ===

Getting RT to serve static content can seem to be quite an issue, especially if it is to be dynamically created such as the ACME challenge/response that [http://letsencrypt.org LetsEncrypt's] certbot uses. The solution is quite simple. In your RT_SiteConfig.pm you can add the StaticRoots directive to serve static pages. Follows is an example of how to use this feature for obtaining certbot authorised requests:
<nowiki>
Set( @StaticRoots,
{
path => sub { s!^/.well-known/!! },
root => '/usr/local/share/html/.well-known/'
},
);</nowiki>

After restarting your RT server, you can then issue a certbot request as follows:
<nowiki>
certbot certonly --webroot -w /usr/local/share/html -d <your domain or rt hostname></nowiki>

'''Note:''' This assumes '/usr/local/share/html' is your document root, change as appropriate to your site, it does '''not''' have to be the location of your RT server or files.

You can then install the certificate in your webserver as per it's documentation, by default the keys and certificates will be located in:
<nowiki>
/etc/letsencrypt/live/<your domain or rt hostname>/fullchain.pem
/etc/letsencrypt/live/<your domain or rt hostname>/privkey.pem</nowiki>
To finish the installation and make certificate renewals automatic on UNIX you can add the following to crontab:
<nowiki>
2 2 1 * * /usr/local/bin/certbot renew --webroot -w /usr/local/share/html -d <your domain or rt hostname> && service apache24 restart</nowiki>

Certbot

2019-02-15T00:15:01Z

Mis: Quick config except on how to make RT play nice with certbot to get free LetsEncrypt SSL certificates

=== Returning content NOT in RT such as ACME challenges for certbot ===

Getting RT to serve static content can seem to be quite an issue, especially if it is to be dynamically created such as the ACME challenge/response that [http://letsencrypt.org LetsEncrypt's] certbot uses. The solution is quite simple. In your RT_SiteConfig.pm you can add the StaticRoots directive to serve static pages. Follows is an example of how to use this feature for obtaining certbot authorised requests:
<nowiki>
Set( @StaticRoots,
{
path => sub { s!^/.well-known/!! },
root => '/usr/local/share/html/.well-known/'
},
);</nowiki>

After restarting your RT server, you can then issue a certbot request as follows:
<nowiki>
certbot certonly --webroot -w /usr/local/share/html -d <your domain or rt hostname></nowiki>

'''Note:''' This assumes '/usr/local/share/html' is your document root, change as appropriate to your site, it does '''not''' have to be the location of your RT server or files.

You can then install the certificate in your webserver as per it's documentation, by default the keys and certificates will be located in:
<nowiki>
/etc/letsencrypt/live/<your domain or rt hostname>/fullchain.pem
/etc/letsencrypt/live/<your domain or rt hostname>/privkey.pem</nowiki>

Main Page

2019-02-14T23:56:41Z

Mis: /* Common problems */ Putting in a small page to describe how to get certbot to work as just spent too much time trying to get it to work myself.

== RT ==

RT is an open source issue tracking and workflow platform developed and supported by [https://bestpractical.com Best Practical Solutions]. This wiki site is a free resource for the RT community to share ideas, configurations, and customizations to RT, RTIR, and related products.

Please: [[UpdateTheWiki]], post your hints, tricks, tips and tools about how to get the most out of RT. If you currently use RT, please head over to [[RTUsers]] and add yourself and your organization to the user list.

== Wiki Move ==

We've recently migrated the RT wiki and all of its content from an instance hosted by Wikia to this instance. If you had a user account on the previous wiki, you'll need to [[Special:UserLogin|create your account again]]. However, all of your content has been migrated over. If you were a contributor on the previous wiki and you see things are out of place, please feel free to rearrange things and fix them up.

We're tracking details from the move on the [[Wikia Move]] page.

== Other Documentation ==

In addition to the information found here, you can find more RT's documentation in your install of RT on the server and also [https://bestpractical.com/resources/ on the web at the Best Practical website]. The [https://bestpractical.com/blog Best Practical blog] is another great resource for RT information.

== Sections ==

You can go through these pretty much in order if you're starting from scratch, but please plan to spend some quality time with the [[UserManual]] before you try to go live; RT is big and full of tons of features, and you probably can't get your head around all of it in one sitting.

* [[FAQ]], [[FindingAnswersAboutRT]] and "Common Problems" below.
* [[BugReporting]]
* [[HowToHelp]], [[Translation]]
* [[Demo]]
* [[UserManual]], [[RTGlossary]] & [[Documentation]]
* [[InstallationGuides]], [[RTTutorials]]
* [[RT Config|RT_Config]] & [[RT SiteConfig|RT_SiteConfig]]

* [[Extensions]] to RT available as installable plugins
* [[Contributions]] by the community to customize RT
* [[RTIR]] RT for Incident Response
* [[RTFM]] RT FAQ Manager

* [[RTHistory]]
* [[InThePress]]
* [[REST]] API
* Customizing with [[CustomizingWithCallbacks|Callbacks]]

=== Common problems ===

* [[CantLocateObject]] - Can't locate object method "new" via package "<code>RT::Handle</code>" at rt3/lib/RT.pm
* [[NoConnectionToSyslog]] - no connection to syslog
* [[NoRecipFound]] - No recipients found. Not sending
* Getting information out of RT3 for [[reporting]] or inclusion elsewhere.
* [[PermissionDenied]] emails|
* Getting RT4.x to play nice with LetsEncrypt's [[certbot]] for free SSL certificates.

== Wish lists ==

* [[WikiWishList]] - wish list for this wiki
* [[WishList]] - wish list for the RT
* [[RT3StatisticsPackageWishList]]

== Getting started with MediaWiki ==

To learn more about how to edit wiki pages, click the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents Help] link here or in the navigation on the left.

We have installed the Markdown plugin, so you can edit pages in Markdown.