When I create and or save content on my drupal site, it drops the port number "my site is website.com:654" and gives the following link in the address bar, which I have no idea where it's coming from. I see "website.com/?q=node%2F177&268056720=1", instead of "website.com:654/whatever". This site I have been developing for a month, and up until a few minutes ago, I could save and edit content with no issue. NOW, when I do try to save anything, it just goes to "website.com/?q=node%2F177&268056720=1" without my port number. And what exactly is the "?q=node%2F177&268056720=1" part???

Comments

arhak’s picture

arhak commented
Status: Active » Postponed (maintainer needs more info)

I can't tell you what 268056720=1 fragment is about, looks like a cache-skip variable set to true

but ?q=node%2F177 means
-- ?q=node/177 (equivalent to node/177 when clean_url is enabled)
-- you don't have clean URL enabled anymore

try going to variable table (e.g. through phpMyAdmin) and set clean_url variable to s:1:"0";
this will make the system know that rewrite rules are not available
then check how does your site behave and post back

lejon’s picture

lejon commented

Hi,

I have the same issue after switching servers with 6.15.

I tried your suggestion and my whole site went to 500 error. I changed it back clean_url variable to s:1:"1"; and now whole site down. With 500 internal server error, even with trying to access ?q=admin.

Any ideas how to get my site back?!

arhak’s picture

arhak commented

@#2 changing a value in a table does NOT causes http error 500

the source of that problem is related to another configuration issue (internal server config) with by chance coincided with time you edited the variable

if it is a misconfiguration of your hosting provider I can't take a guess on the fly
but thinking the fault might come from your fingertips the best guess would be improper edition of the .htaccess file (invalid rules or combination of rules)

backup the current .htaccess you have (if it is customized by you or your developers some how) and try restoring that file from a fresh Drupal install, check if the site comes back (to the same previous status)

also you can ask for support to your ISP even when they might not been related to what caused it, but as their client you have the right to ask them if they did something or if you're the culprit

dpearcefl’s picture

dpearcefl commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

Closing due to lack of response. Problem solved already?