Vahan 139 2 Link Link Jun 2026
According to the rule, these documents can be produced or sent by registered post to the concerned authority within that period. This rule is designed to provide relief to drivers who may have forgotten a document at home.
Ensure your vehicle is already registered on the Vahan 4.0 database. If it is an old vehicle, you may need to visit your local RTO to digitize the records.
If you want, I can:
If you have ever tried to navigate the world of Indian vehicle registration or permit management, you have likely come across the term . Specifically, "Vahan 139 2" refers to a specific entry point or server link within the Vahan 4.0 ecosystem managed by the Ministry of Road Transport and Highways (MoRTH). vahan 139 2 link
The Vahan portal represents a significant step towards digital transformation in the transport sector in India. Services like those potentially linked through "Vahan 139 2 link" are designed to make life easier for citizens by providing quick and efficient access to vehicle and driving-related services.
The Vahan portal is the central hub for many vehicle-related services, including:
This section details the workflow used by Transport Department users (RTO/EO) when interacting with this module. According to the rule, these documents can be
: Digital versions of these documents are valid if presented via official government apps like mParivahan DigiLocker , which pull data directly from the and SARATHI databases. Grace Period
While the Vahan 139 2 link has made it easier to track and monitor vehicles, there are some common issues that vehicle owners may face. Some of these issues include:
The phrase "vahan 139 2 link" seems to be related to a specific topic or query, but without additional context, it's challenging to provide a detailed write-up. However, I can attempt to break down the components and offer a general explanation or possible interpretation. If it is an old vehicle, you may
For assistance, visit your nearest RTO or contact State Transport Department.
, be extremely careful. Fraudsters often use official-sounding terms like "Vahan" and "Rule 139" to trick people into clicking phishing links or downloading malicious files (.apk). 🛡️ Critical Safety Review The Legitimate Rule:
The '139 2' in your search refers to Rule 139 of the Central Motor Vehicles Rules, 1989. This is a crucial legal provision that every vehicle owner should know.
In the context of Indian motor vehicle regulations, of the Central Motor Vehicles Rules (CMVR), 1989, focuses on the production of license and registration certificates. A critical update to this rule was introduced in 2018 to facilitate digital documentation. Overview of Rule 139
Ben Whitmore
Simon Skotheimsvik
Sandy Zeng
Hello,
We followed your guide to the letter on a 2016 and 2019 server but we keep running into the problem that the SCEP application pool keeps crashing for no real reason. We already ruled out a mistake in the templates or wrong CA certs in the intermediate.
We can see the Cert requests arrive but IIS dies everytime we see this in the NDES log:
NDES COnnector:
Sending request to certificate registration point. NDESPlugin 18-4-2019 17:04:05 3036 (0x0BDC)
Event viewer just shows us that w3wp.exe has crashed and that the faulty module is ntdll.dll.
We’ve been banging our heads against this problem for a week now so we hope you have any idea where to look.
Regards,
Herman
Nick, your stuff is amazing as always! .NET 3.5 appears to be required, so may be worth mentioning somewhere since some installations will need to specify an alternate path for that.
Using your script, I was failing on “Attempting to install Windows feature: Web-Asp-Net” and it wasn’t until I manually added 3.5–specifying the alternate path to the Server installation media–that I could continue.
Appreciate you sharing your findings Matt.
Regards,
Nickolaj
Internalurl in the app proxy config should be https and not http.
Yes, you’re correct.
Regards,
Nickolaj
Does this work for Android for Work or Android Enterprise devices? I can’t find the certificate issued to the end mobile devices even – iOS?
Yes it works for all platforms you mention.
Regards,
Nickolaj
Hey Nickolay,
there are two mistakes in your two pictures showing the configuration of the AAP. In the internal URL field you have to write https instead of http, because of the later binding / requiring of SSL. Your other older posts showing this also with https configured.
Best regards and nice work!,
Philipp
I’ve wasted way too much time troubleshooting this before I checked the IIS log files and they showed port 80. After changing AAD Proxy to HTTPS everything works.
Great guide though!
It appears that the script is expecting to find only 1 client authentication certificate with the specified subject. Could you modify it to handle cases where there are multiple certificates with the same subject?
Hello – Is there a mistake with the steps regarding the client and server certificates? At first you emphasized the points of each type which in turn have different Extended Key Usages. Are you stating to use the same template that contains both types?
Hi Carlos,
Could you please reference the pieces that you’re talking about?
Regards,
Nickolaj
Awesome step by step guide, many thanks. As per usual the MS TechNet lacks a lot of steps and inside information. Regarding the two certs, can they also be 3rd party and trusted certs (wildcard) ?