A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 6

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 7

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 8

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 9

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 10

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 11

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 284

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 291

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 306

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 316

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 317

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 318

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 319

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 377

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 110

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 143

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

NRIPage | Articles | Tourist Alleges Assault Near Madgaon, Goa; Sparks Outrage, Safety Concerns Among Travelers | Get Education & Training Articles. Empowering Lifelong Learning around the world - NRI Page
Edit

Tourist Alleges Assault Near Madgaon, Goa; Sparks Outrage, Safety Concerns Among Travelers

Tourist Alleges Assault Near Madgaon, Goa; Sparks Outrage, Safety Concerns Among Travelers

A distressing incident near Madgaon railway station in Goa has triggered a wave of concern among travelers, after a tourist shared an account of being physically assaulted and verbally abused by two local men. The man, who detailed his experience in a viral Reddit post titled “Got physically abused in Goa, will probably never come back,” said the encounter has left him deeply disturbed and unwilling to revisit the popular tourist destination. According to the tourist, who was traveling with his girlfriend, the situation escalated over a minor traffic issue. After dropping his girlfriend at Goa International Airport (GOI), he was driving towards Madgaon railway station to catch a train. He claimed that two locals on a two-wheeler accused him of “cutting them off,” although there was no physical contact between the vehicles. “No bump, no scratches, our vehicles did not touch,” he clarified.
 

However, the matter did not end there. The two men allegedly followed him to the station, blocked his car, and began threatening him. One of them reportedly picked up a stone and demanded that the tourist roll down his window. When he complied, he said he was immediately punched and subjected to a stream of verbal abuse. “The moment I opened it, he punched me straight up. His other friend was just standing and both were abusing me about me being from outside,” he wrote in the post. The man said he had only a few minutes left to return his rental car and board his train. Fortunately, a few bystanders intervened, allowing him to leave the scene. He concluded his post by saying that the experience has “scarred” his perception of Goa. “I hate Goa now because of this and it has scarred all the good times I had,” he lamented. While he expressed a desire to file a police complaint, he admitted he was unable to record the incident or gather any identifying information about the attackers.
 

Online Reactions: Fear, Frustration, and Disillusionment

The incident has gone viral on social media and travel forums, with many users expressing shock and anger over the rising number of such reports from Goa. Some longtime visitors and Goa enthusiasts shared similar experiences, fueling concerns about tourist safety in the state. “I am gutted. I have loved Goa since my college days… but I don't think I will visit anymore,” wrote one user. Another remarked, “Mob justice and vigilantism is the new culture… not just in Goa, but across the country.” The situation has brought to light a growing frustration among travelers regarding local behavior, transport issues, and a perceived decline in Goa's hospitality. “Local taxis charge a bomb,” one user pointed out, while others echoed that the state has become increasingly stressful for tourists who are not locals or who do not have private connections.
 

Several users also mentioned facing similar hostility from locals in previous visits, although not all escalated into physical violence. “This was my 9th visit and yes, like you, the last,” commented one user. Others noted that Goa’s charm has been steadily deteriorating due to rising commercialization, lack of reliable public transport, and increasing reports of aggressive behavior toward outsiders — especially those involved in minor disputes.
 

At the time of writing, no official complaint had been registered with the local police regarding this specific incident. Authorities have not issued any statement in response to the claims. However, the widespread attention the story has received online may prompt further inquiries or official comments in the coming days. This incident adds to a growing list of concerns for Goa’s tourism image, especially as the state heavily relies on domestic and international tourists for economic activity. With peak travel seasons often attracting millions of visitors, maintaining a secure and welcoming environment has become more crucial than ever. Whether this incident leads to systemic changes or increased scrutiny remains to be seen, but for now, it has left a lasting impression on many would-be visitors questioning whether Goa remains the safe haven it once was.

What is your response?

joyful Joyful 0%
cool Cool 0%
thrilled Thrilled 0%
upset Upset 0%
unhappy Unhappy 0%
AD
AD